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
Provide the ability to search for a setting to change #872
Comments
Comment 1 by jteh on 2010-09-01 21:56 |
Comment 2 by RamboUdin on 2010-09-06 03:07 |
This is a nice follow up for #577. |
Now #577 has been included this would be a nice feature for 2019.2. |
I'm afraid this is much more complex than you may think. @feerrenrut once proposed a major change to the way the setting gui is created from a code perspective, and I think such a major change would be required to implement this effectively. |
Yes, there are quite a few challenges to do this. There is of course the technical challenge of how to go from what we have now to what would be required to implement this feature. There are also a lot of UX challenges. To progress this issue, I think it would be good to see a minimal prototype. I would suggest implementing this prototype with as little of the baggage in the NVDA GUI as possible, then as a secondary consider how to go from what we have to this approach. Some UX to consider:
I have some initial ideas, but I have not worked through them to see if they are feasible:
|
the discussion appears to me to be a case of trying to do too much. Not being a programmer, this might not be practical but here is my modest proposal: You would be in exactly the same place in the dialog and you would activate the ok button in exactly the same way or you would tab or shift tab to work with other settings in the dialog. Perhaps the search could be made more specific. The user might type pitch, down arrow and find pitch in the list and press enter. The user would then be on the pitch slider. The same with speed or whatever else is available in the dialog. Gene |
Hi, That's what I would imagine would be the case (perhaps that might be the UI a potential prototype might present)... except we need to be more specific about implementation strategy. Reef provides some thoughts about implementation strategy (see his notes above for details), but to siplify it a bit, it reuqires working with a combination of wxPython features and the capability NVDA provides. Thanks. |
@Gene703122 one issue here is there are different kinds of matches. Let's imagine the results for the search term "speech"
The user may be trying to find a specific configuration control like "Speech interrupt for typed characters ", or just a shortcut to the speech settings panel. If all of the config controls from the speech settings panel are included (speed, pitch, voice, etc) it will be slow to find other "primary" search results such as "Speech interrupt for typed characters". If the contents of matching groups or panels are excluded, but a way to jump directly to that settings panel or group is included, this is basically the second suggestion I made (quoted here for reference):
I would now adjust this, last time I tested the |
Just bumping this thread. |
I would also like to see this for the following reasons:
Thanks. |
Reported by etman98 on 2010-09-01 21:52
Hello,
I don't always like going into the NVDA Menu every time to change a setting. If I want to change the synthasizer then connect a braille display I have to go to the synthasizer dialog then when done, go back into the NVDA Menu go to preferences, then go to braille settings. Could you turn the NVDA Menu into a dialog with a menu bar & search box to search for a setting to change?
Thanks!
The text was updated successfully, but these errors were encountered: