Daniel Dalton wrote:
Are there 3 or 4 items?
Four.
And why can't the button used to leave the
quickscreen be used to voice time then it can imediately exit?
Some people use voice, and this shouldn't alter their ability to use the
quick screen. The quick screen is for quick changing of settings, and
waiting for a voice to speak would slow this down.
If this
is such a big problem remembering nothing will change if voice is
disabled, we could make a long press (BUTTON_REPEAT), say time and
BUTTON_REL (a tap), could leave the screen?
This would make more sense, though it would make more sense if the
long-press were a function actually related to the quick screen. As the
screen doesn't even display the time itself, having a button combo to
announce it there doesn't make much sense from a usability standpoint
for sighted users, and just adding voiced things to random places
"because there's a button free there" doesn't lead to a very coherent
design. Is there a problem with the existing time screen, or is it
simply a case of "it's too far away?"
Note after the time is voiced, the screen should auto exit.
This would be a bad idea. If time can be announced there, it shouldn't
change the state of the player, just announce the time. Generally
speaking, it's a bad idea to have buttons perform multiple actions
unless it's necessary to do so, especially if those actions wouldn't
necessarily be expected. There doesn't seem to be any reason why a
long-press can't simply read the time but leave it in the screen.
