View Single Post
Old 10-22-2016, 03:12 AM   #39
Josieb1
Grand Sorcerer
Josieb1 ought to be getting tired of karma fortunes by now.Josieb1 ought to be getting tired of karma fortunes by now.Josieb1 ought to be getting tired of karma fortunes by now.Josieb1 ought to be getting tired of karma fortunes by now.Josieb1 ought to be getting tired of karma fortunes by now.Josieb1 ought to be getting tired of karma fortunes by now.Josieb1 ought to be getting tired of karma fortunes by now.Josieb1 ought to be getting tired of karma fortunes by now.Josieb1 ought to be getting tired of karma fortunes by now.Josieb1 ought to be getting tired of karma fortunes by now.Josieb1 ought to be getting tired of karma fortunes by now.
 
Posts: 5,094
Karma: 18051062
Join Date: Nov 2009
Location: UK
Device: Kindle Scribe, Coloursoft, PW SE, Kindle 6, Kobo Libra 2, Clara BW
Quote:
Originally Posted by Axanar View Post
I was one of the people who complained about the difficult readability of the system text. This was caused by Amazon changing the "bold'ish" shape of the fonts. this has been adressed by 5.7.x.

The capitalization was never questioned. At least not by me. The capitalization of dialog buttons isn't necessary because the dialog buttons already had "bigger" and "bolder" fonts. But even so, this can still be accepted.


The main issue here is "not" the "X". The issue is that most dialogs (let's call them window) inside the Kindle firmware are inconsistent in their visual appearance.

In case I explained myself not good enough (I am german). Let me try a different attempt of explaining it.

Right now the Kinde firmware (as of 5.8.5) has plenty of inconsistent windows and this is most likely an issue of lack of quality control and/or wrong people working at wrong parts of that firmware.

Right now we have windows (remember: dialogs) with buttons applied at the bottom that allows you to confirm or close the window. We have windows with said "X"'es at the top right (and badly laid out too) that allows you to close these windows. We have windows without "X"'es and/or confirmation buttons at the button, where you need to tab outside to close them.

These are by now 3 different visual appearances and 3 different ways of closing the window.

Example1:
Click on the Lens at the top (search). Look at the window there. The "X" is outside of said window. In former Kindle firmware versions, this window looked similar to other windows having the "X" inside a framed window.


Example2:
Go to Settings->Device Name->(Arrow to change the name)

You get a window with two *frameless* buttons at the bottom (besides the textfield to change the name of your device). One says "ABORT" the other says "SAVE" (Capital letters: or similar wording: I have my Kindle running in german language).

Now go to Settings->Social Networks->Facebook/Twitter

You get a window with two *framed* buttons at the bottom. The buttons are *first char capitalized* saying "Abort" and "Continue" (aha? not capitalized?).

This is inconsistent, compared to the other windows.

Example3:
Go to Settings->Device options->Device info. A window pops up showing an "X" at the top right and a *frameless* button on the bottom right saying "NEWS".

Now looking at Exampe 2 again. There was no "X" at the top right, instead there was an "ABORT" button at the bottom left.

Making two similar window look "inconsistent".

If you look around in the settings, then you may get more of these inconsistencies.

Example4:
Erasing WIFI-Passwords window. It has two frameless buttons at the bottom. One says "ABORT" the other "ERASE". Here you can not tab outside the window to close it.

They are playing with "windows" (the type of objects that catches the entire kindle screen with e.g. buttons at the bottom). They deal with "modal" dialogs (the ones that doesn't allow tabing outside to close the window), they are dealing with other types of dialogs having an "X" inside etc.

Even different wording for same "effects".

I find this highly distracting.
I, at least for the next six weeks, test software for a major organisation. I worked through Examples 1-3. IF they had been spotted in testing, and that would only be if the same team or testers tested all three examples, or if the results didn't match the test scripts or documentation (not an automatic given here) then they would no doubt be marked as cosmetic and made a low priority, or even postponed to fix at a later date.

I get that it bugs you but the functionality works, it's just cosmetically they don't match.

NB: I said six weeks as I'm being made redundant. (Yes I'm happy)
Josieb1 is offline   Reply With Quote