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
This is a feature request for the return of the insert-ctrl-I hotkey to invoke the "input gestures" dialog #3604
Comments
Comment 1 by jteh on 2013-10-23 19:19 I guess it can be left as an unbound command, though this would probably need to be documented somehow in the User Guide and I can't think of a good way to do this. It could also be done in an add-on. |
Comment 2 by dgoldfield on 2013-10-24 14:53 |
Comment 3 by MHameed on 2013-10-24 15:50 |
Comment 4 by jteh on 2013-10-24 23:37 How do you propose we document unbound commands? I suspect that will lead to a lot of confusion. It's particularly problematic for settings dialogs because they include their key binding in brackets inside the heading. If we write (unbound) or something, the obvious question is, "What does that mean? How do I bind it?" |
Comment 5 by nvdakor on 2013-10-25 00:11 |
Comment 6 by dgoldfield on 2013-10-25 00:17 |
Comment 7 by jteh (in reply to comment 6) on 2013-10-25 05:06
Such a long piece of text doesn't fit nicely. It's also biased to keyboard, but NVDA supports touch as well. In addition, it needs to indicate that it can be assigned, not just that it isn't, since there are some settings that can't be assigned. |
Comment 9 by jteh on 2015-02-09 02:16 |
Reported by dgoldfield on 2013-10-23 18:46
I feel that having a hotkey to invoke the "input gestures" dialog was a wonderful feature and I was sorry to see that it was removed. It is much easier to bring up the dialog in this way as opposed to going through the menus. At the very least, would the development team consider having the key as being unassigned in the default configuration? this would give users the choice of assigning it if they wanted to use it; otherwise, there would be no functional change in the program.
Blocked by #4898
The text was updated successfully, but these errors were encountered: