You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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.
The text was updated successfully, but these errors were encountered: