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

Touchscreen support: add an option to not allow NVDA to activate touch keyboard keys when performing hover gesture #7309

Open
josephsl opened this Issue Jun 21, 2017 · 1 comment

Comments

Projects
None yet
1 participant
@josephsl
Collaborator

josephsl commented Jun 21, 2017

Hi,
I think some in the community have requested this:

There are times when one would like to explore the touch keyboard without pressing keys. This can be done by modifying the hover gesture to not activate the object, with this being configurable.

Thanks.

@josephsl

This comment has been minimized.

Collaborator

josephsl commented Jun 21, 2017

Hi,

Implementation details: a new confspec section and an associated dialog should be added to control this behavior. I suggest "touch" as the confspec section name, as it could be extended to cover input from say, touchpads, Surface Dial and what not.

CC @michaelDCurran

Thanks.

josephsl added a commit to josephsl/nvda that referenced this issue Jun 22, 2017

josephsl added a commit to josephsl/nvda that referenced this issue Jun 23, 2017

josephsl added a commit to josephsl/nvda that referenced this issue Jul 28, 2017

User guide: includethe fact that tablets display touch keyboard when …
…keyboards are undocked. re nvaccess#7309.

A reminder from Mick Curran (NV Access): for tablets such as Microsoft surface Pro and others, when the computer is in tablet mode or keyboard is undocked, touch keyboard becomes visible and stays on top at all times.

josephsl added a commit to josephsl/nvda that referenced this issue Dec 5, 2017

Touch handler and GUI: check if touch is supported, as touch handler …
…might not be ready when initializing GUI subsystem. re nvaccess#7309.

Touch handler is initialized AFTER GUI, so handler might not be ready at all. To avoid this, a new touchHandler.touchSupported function will be used to check if touch interaction is supported. For now, it is used by GUI, but add-ons and other modules are more than welcome to use it."

josephsl added a commit to josephsl/nvda that referenced this issue Dec 5, 2017

Touch handler: use max touches constant (95) as a proper constant. re n…
…vaccess#7309.

Noted by Mick Curran (NV Access): because the literal '95' is used multiple times, give it a proper label and use it as a constant.

michaelDCurran added a commit that referenced this issue Dec 20, 2017

Touch keyboard support: ability to configure how the key is pressed v…
…ia hover up (tuch typing) or double-tap (standard typing) (#7316)

* Touch support: add a new map for touch interaction settings such as standard versus touch typing and what not. re #7309.

* Global commands/hover up: press the touch key if touch typing option is enabled.

By default, touch typing will be disabled, but can be enabled by changing touch interaction settings.

* Touchscreen/touch typing: add a new Touch Interaction dialog to configure touch typing mode between touch and standard.

Instead of just calling this 'touchscreen settings', touch interaction settings is a more appropriate title as it may include other interaction methods and settings in the future.

* User guide: document the new touch interaction dialog and added a section on using the touch keyboard.

* Touch interaction: only add this dialog if and only if touchscreen support is in use. re #7309

* Fix translator comment mispelling.

* Touch Interaction: make sure to call the correct super function for the correct dialog class.

* User guide: includethe fact that tablets display touch keyboard when keyboards are undocked. re #7309.

A reminder from Mick Curran (NV Access): for tablets such as Microsoft surface Pro and others, when the computer is in tablet mode or keyboard is undocked, touch keyboard becomes visible and stays on top at all times.

* Touch interaction dialog: add translator comment for the tooltip.

A word from Mick Curran (NV Access) to add translator comments in order for scons checkPot to pass.

* Touch handler and GUI: check if touch is supported, as touch handler might not be ready when initializing GUI subsystem. re #7309.

Touch handler is initialized AFTER GUI, so handler might not be ready at all. To avoid this, a new touchHandler.touchSupported function will be used to check if touch interaction is supported. For now, it is used by GUI, but add-ons and other modules are more than welcome to use it."

* Touch handler: docstring

* Touch handler: use max touches constant (95) as a proper constant. re #7309.

Noted by Mick Curran (NV Access): because the literal '95' is used multiple times, give it a proper label and use it as a constant.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment