This feature request comes from a discussion on a French mailing list.
Is your feature request related to a problem? Please describe.
The user has accidentally locked one of the mouse button with shift+PavNum*without realizing it while working in Windows Explorer. Then he noticed unexpected behaviors such as arrow keys not working or not reporting anything when trying to navigate in Windows Explorer.
He has tried to restart NVDA but this did not solve the issue. Thus he was thinking to a Windows issue.
Describe the solution you'd like
The user suggests the following solution:
When exiting NVDA with insert +q, NVDA should unlock the mouse buttons if the button was originally locked by an NVDA command.
Describe alternatives you've considered
The real issue is that a screenreader user may forget that he has locked a mouse button with a screenreader command. On the contrary, a mouse user does not forget to release the pressure on the mouse button when needed.
Other solutions to this issue can be thought. For example a sound notification each 10 seconds to record the user that a button should be unlocked.
Additional context
None
This feature request comes from a discussion on a French mailing list.
Is your feature request related to a problem? Please describe.
The user has accidentally locked one of the mouse button with shift+PavNum*without realizing it while working in Windows Explorer. Then he noticed unexpected behaviors such as arrow keys not working or not reporting anything when trying to navigate in Windows Explorer.
He has tried to restart NVDA but this did not solve the issue. Thus he was thinking to a Windows issue.
Describe the solution you'd like
The user suggests the following solution:
When exiting NVDA with insert +q, NVDA should unlock the mouse buttons if the button was originally locked by an NVDA command.
Describe alternatives you've considered
The real issue is that a screenreader user may forget that he has locked a mouse button with a screenreader command. On the contrary, a mouse user does not forget to release the pressure on the mouse button when needed.
Other solutions to this issue can be thought. For example a sound notification each 10 seconds to record the user that a button should be unlocked.
Additional context
None