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

NVDA should make it easier to discover unbound gestures #1425

Closed
nvaccessAuto opened this Issue Mar 22, 2011 · 3 comments

Comments

Projects
None yet
1 participant
@nvaccessAuto

nvaccessAuto commented Mar 22, 2011

Reported by geoff on 2011-03-22 21:57
When following the instructions in section 12.1 of the NVDA User's Guide,
one expects to see all keypresses in the log, including keycodes which
one might consider binding to a script. Using default settings,
however, only keys which are bound to a script are logged.

One presumably has to change logging to a more detailed level in order
to discover how to specify a desired gesture which is not already bound
to a script.

I suggest that either all gestures should be llogged at the default
logging level when in input help mode, or that the user guide be updated
to include instructions on setting the correct logging level needed to
see unbound gestures before entering input help.

@nvaccessAuto

This comment has been minimized.

nvaccessAuto commented Mar 22, 2011

Comment 1 by jteh on 2011-03-22 21:58
Changes:
Milestone changed from None to 2011.2

@nvaccessAuto

This comment has been minimized.

nvaccessAuto commented Apr 5, 2011

Comment 2 by mdcurran on 2011-04-05 00:20
Fixed in 277ed77. Now all gestures are logged in input help mode, whether or not they are bound to a script.
Changes:
State: closed

@nvaccessAuto

This comment has been minimized.

nvaccessAuto commented Apr 7, 2011

Comment 3 by jteh on 2011-04-07 05:57
7e6bb88
Changes:
Milestone changed from 2011.2 to 2011.1.1

@nvaccessAuto nvaccessAuto added the bug label Nov 10, 2015

@nvaccessAuto nvaccessAuto added this to the 2011.1.1 milestone Nov 10, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment