Support and General Use > User Interface and Voice
Proposal for a new "yes-no" Dialog
(:@):
I find the yes-no dialog on my h100 a bit confusing. For example if I want to delete a file, the yes-no dialog displays 'PLAY = Yes' and 'Any Other = No'. I always think I have to press the Play-button for 'Yes' but the real button to confirm is the Select-button. Changing the text to 'SELECT (Button) = Yes' wouldn't be much clearer.
My proposal is to implement the yes-no dialog as a menu with two choices: yes and no.
The pros and cons are:
pros:
* clear
* save some bytes (I guess)
cons:
* only one line for the description text
* much work (especially updating the language files)
AlexP:
It should say NAVI = Yes, as this is what it is marked as, and we refer to 'select' as.
There was a patch floating around many moons ago for a Yes/No dialogue - you may be able to find it on the tracker, although I suspect it will be so horribly out of date you may as well start again.
roolku:
I am against it. The current mode is faster, safer and can be operated blindly. With a menu you need to visually check the current selection, potentially make adjustments, wait until you are convinced that the new selection is stable (you didn't accidently overshoot and/or UI lag is not causing a delay in screen update) and then confirm the selection.
If the labelling is wrong for your target, it is easy to edit the language file. In fact it already is target specific:
< source >
*: "PLAY = Yes"
h100,h120,h300: "NAVI = Yes"
ipod*,x5,m5,gigabeatf,e200,c200,h10,h10_5gb: "SELECT = Yes"
player: "(PLAY/STOP)"
< /source >
if it doesn't work for you, there is a bug somewhere.
(:@):
Concerning the "NAVI = Yes": It's my fault (maybe a bug in my own build). I've tested it with an official build and it shows "NAVI = Yes".
--- Quote from: BigBambi on February 14, 2008, 04:41:17 AM ---There was a patch floating around many moons ago for a Yes/No dialogue - you may be able to find it on the tracker, although I suspect it will be so horribly out of date you may as well start again.
--- End quote ---
It's not that important that I want to screw up my build with an old patch. But thank you for the hint.
--- Quote from: roolku on February 14, 2008, 04:57:31 AM ---I am against it. The current mode  is faster, safer and can be operated blindly. With a menu you need to visually check the current selection, potentially make adjustments, wait until you are convinced that the new selection is stable (you didn't accidently overshoot and/or UI lag is not causing a delay in screen update) and then confirm the selection.
--- End quote ---
I don't know if we are talking about the same menu. I don't see the problem operating it blindly, because it will show up as:
Delete xy?
[icon]Yes
[icon]No
Confirm it with select (as it is now) or just move the 'cursor' to the item below and select it. There are only two choices possible, I don't think it will take long to update the selection if 'No' is chosen.
The settings in rockbox can be adjusted through menus and this one is not much different.
JdGordon:
the proposal is certainly not new... that was one of the first thing I patched when I came to the project... it was rejected...
Using the list widget for the yes no screen would actually make it much easier to blind users, when the move up/down it would say "yes" and "no" and the question can be voiced easily. + there should be a binary decrease if this was changed... maybe ill have a play with this tongiht
Navigation
[0] Message Index
[#] Next page
Go to full version