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
Prevent of loosing the NVDA key through incorrect settings #2871
Comments
Comment 1 by jteh on 2012-12-22 23:15 |
Comment 2 by nvdakor on 2013-05-06 23:06 |
Comment 3 by heikofolkerts on 2013-07-16 18:14 |
Attachment 0001-Patch-for-2871-unchecking-all-NVDA-modifier-keys-in-.patch added by heikofolkerts on 2013-07-16 18:16 |
Comment 4 by jteh on 2013-07-16 21:49 |
Comment 5 by Michael Curran <mick@... on 2013-10-01 05:49
|
Comment 6 by Michael Curran <mick@... on 2013-10-01 05:50
Changes:
|
Comment 7 by mdcurran on 2013-10-01 05:52
|
Comment 8 by Michael Curran <mick@... on 2013-10-15 09:54
Changes:
|
Comment 9 by mdcurran on 2013-10-15 09:57 |
Comment 10 by driemer.riemer@... on 2015-05-29 17:57 |
Comment 11 by jteh on 2015-06-01 00:01 |
Reported by aliminator on 2012-12-17 08:29
This happens when in the keyboard settings dialogue following settings are set:
Use CapsLock as an NVDA modifier key: unchecked
Use numpad Insert as an NVDA modifier key: unchecked
Use extended Insert as an NVDA modifier key: unchecked
Then, the NVDA key will not be available anymore.
What about providing an error message box if such configuration is goin to be applied.
Another maybe more effective alternative is to provide a multi-select list box for those settings mentioned.
The text was updated successfully, but these errors were encountered: