You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.
For controls that accept numbers as input, there are several methods to manipulate values:
Strict text entry (currnet implementation)
List (limited to a set of choices)
Spin box: An edit field that allows users to use up and down arrows to change values.
I'd like to propose that we use the third method. Benefits include users not having to worry about entering wrong values as the control itself knows min and max, just using arrow keys to change values, allow touch users to change values by tapping the spin button control and others. The only possible disadvantage I see here is denoting min and max for certain options - for this, a reasonable range should be provided.
The following options could be enhanced via spin boxes:
Sounds good. For braille settings I've wondered why they weren't spinners before. But the min/max should be obtained from the config structure if at all possible. By the way, the braille cursor blink rate currently doesn't have a sane minimum (100 or even 200ms should work).