New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GUI: use spin boxes for number entry fields such as message timeout in braille dialog and others #6099
Comments
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). |
We should give the wx.SpinCtrl a go, this would be a quick fix if wx.SpinCtrl is acceptable from an accessibility standpoint. |
feerrenrut
added a commit
that referenced
this issue
Sep 30, 2016
For numerical input fields a wx SpinCtrl is now used. The min/max values come from the nvda config schema validation (if available).
feerrenrut
added a commit
that referenced
this issue
Oct 12, 2016
feerrenrut
added a commit
that referenced
this issue
Oct 27, 2016
Spin Controls are now used for numerical input fields. (#6099)
josephsl
added a commit
to josephsl/nvda
that referenced
this issue
Oct 28, 2016
…access#6520 Specifically: * nvaccess#5906: Now labeled as 'line indentation reporting'. * nvaccess#6099: clarify how to change values in spin controls. * nvaccess#5886: elements list is available in browse mode. * nvaccess#6206: changed bits such as 'adding new entries'. * nvaccess#6127: no more hyphen (dash). * nvaccess#5050: 'causes' -> 'which caused'. * nvaccess#4164: changed wording to reflect that read-only edit fields are now included.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
For controls that accept numbers as input, there are several methods to manipulate 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:
Thanks.
The text was updated successfully, but these errors were encountered: