Prevent of loosing the NVDA key through incorrect settings #2871

Closed
nvaccessAuto opened this Issue Dec 17, 2012 · 12 comments

1 participant

@nvaccessAuto

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.

@nvaccessAuto

Comment 1 by jteh on 2012-12-22 23:15
Should be done, but not a major concern, since you can access the NVDA menu via the icon in the notification area.

@nvaccessAuto

Comment 2 by nvdakor on 2013-05-06 23:06
Hi,
I can see why it is trivial. However, if all modifier checkboxes are unchecked, user will no longer be able to execute commands which involves NVDA modifier key. I think perhaps a warning dialog about unchecking all modifier checkboxes would solve this problem (if the user answers no, then the user would be returned to keyboard settings dialog with fir modifier checkbox on focus).

@nvaccessAuto

Comment 3 by heikofolkerts on 2013-07-16 18:14
the fix checks wether all three checkboxes for the NVDA modifier keys are unchecked and gives an error message when the user presses OK. Implementing a multiselect option would be more complex and trickier to understand for new users.
Changes:
State: closed

@nvaccessAuto

Attachment 0001-Patch-for-2871-unchecking-all-NVDA-modifier-keys-in-.patch added by heikofolkerts on 2013-07-16 18:16
Description:
The patch created by git to fix this ticket.

@nvaccessAuto

Comment 4 by jteh on 2013-07-16 21:49
Thanks for the patch. The ticket should remain open until the fix is accepted and committed.
Changes:
State: reopened

@nvaccessAuto

Comment 5 by Michael Curran <mick@... on 2013-10-01 05:49
In [1406623]:
```CommitTicketReference repository="" revision="140662354839caf523b60bc6bf7b33d8e3d670b0"
unchecking all NVDA modifier keys in the keyboard settings dialog should give an error. Exact patch re #2871

@nvaccessAuto

Comment 6 by Michael Curran <mick@... on 2013-10-01 05:50
In [0487efb]:
```CommitTicketReference repository="" revision="0487efb61ab03a84d4b86e45756d1a94778dc6b4"
Merge branch 't2871' into next. Incubates #2871.

Changes:
Added labels: incubating
@nvaccessAuto

Comment 7 by mdcurran on 2013-10-01 05:52
Thanks for the patch. I cleaned a few little things up:

  • use log.debigWarning rather than log.error as this is not an actual unexpected error in NVDA.
  • use not x rather than x == false in several places. Same meaning but slightly shorter.
  • Cleaned up message wording a little.
@nvaccessAuto

Comment 8 by Michael Curran <mick@... on 2013-10-15 09:54
In [01e75f9]:
```CommitTicketReference repository="" revision="01e75f9458469dd3543bd434daa8a18d2213a6d7"
Merge branch 't2871'. Fixes #2871

Changes:
Removed labels: incubating
State: closed
@nvaccessAuto

Comment 9 by mdcurran on 2013-10-15 09:57
Changes:
Milestone changed from None to 2013.3

@nvaccessAuto

Comment 10 by driemer.riemer@... on 2015-05-29 17:57
Since this is closed, can the keywords be removed to simplify for those of us who are trying to find tickets to review?

@nvaccessAuto

Comment 11 by jteh on 2015-06-01 00:01
Sure, though it's fairly easy to simply search for needsCodeReview and status is not closed, so I'm not going to bother doing this for all tickets.

@nvaccessAuto nvaccessAuto added this to the 2013.3 milestone Nov 10, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment