Skip to content
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

Jump to bottom

Introduce a "pass through" mode for touch gestures #3779

Open
nvaccessAuto opened this issue Jan 15, 2014 · 6 comments
Open

Introduce a "pass through" mode for touch gestures #3779

nvaccessAuto opened this issue Jan 15, 2014 · 6 comments
Assignees
@michaelDCurran
Labels
enhancement feature/touch-screen

Comments

@nvaccessAuto
Copy link

Reported by k_kolev1985 on 2014-01-15 11:09
Since I've started using NVDA on a portable computer with a touch screen running windows 8.1, I've noticed that while NVDA is running, some of the touch gestures of the operating system cannot be performed. Examples of such gestures are:

  • Touch and hold (eg. for invoking a context menu).
  • Scrolling of lists and other similar controls (even with 2, and not only with 1 finger).
  • Activating controls, witch don't have defined actions for them (even triple tapping does not work on such controls).

Yes, there's a "pass through" command in NVDA, but:

  • It works only for keyboard commands and not for touch gestures.
  • It can be invoked by default only from the keyboard and if the touch screen device does not have a keyboard, the command can't be invoked. Maybe we can assign a touch gesture to the "pass through" command via NVDA's settings, but I haven't tested that yet.

So, can something be done so the "pass through" command will work for touch gestures as well, and not only for keyboard commands?

My configuration:

  • NVDA: latest next snapshot (same results with the stable 2013.3 version).
  • Operating system: Windows 8.1, 32-bit, with regional and language options set to "bulgarian".
  • Device: ASUS Transformer Book T100.
@nvaccessAuto
Copy link
Author

Comment 1 by nvdakor on 2014-07-06 12:13
Hi,
From examining touchHandler and keyboardHandler, what I can tell is that we need a way to let touch handler know not to treat next gesture as NVDA gesture. As you said, there is a script that allows next keyboard command to be passed through the operating system, but this only calls passthrough on keyboard at the moment. So in order to fix this, we need to first add a method (one or more) that'll let touch handler not deal with the next gesture, and call this method in passthrough script so touch can be taken care of.
Thanks.

@nvaccessAuto
Copy link
Author

Comment 2 by jteh (in reply to comment 1) on 2014-07-06 22:53
Replying to nvdakor:
With keyboard, the hook can specify whether a key should pass through. I can't see any explicit way to do this for touch. Maybe calling DefWindowProc instead of returning 0 will work, but I doubt it. Failing that, we might have to re-inject gestures, but that is far from ideal and could cause unexpected results.

@nvaccessAuto nvaccessAuto mentioned this issue Nov 10, 2015
Closed
@bhavyashah
Copy link

@josephsl Since you were analysing this feature request from an implementation standpoint in #3779 (comment), could you please respond to certain concerns that @jcsteh expressed in the same regard in #3779 (comment)?

@josephsl
Copy link
Collaborator

josephsl commented Sep 5, 2017 via email

@Qchristensen
Copy link
Member

As touch-screen devices become more prevalent, we're starting to get asked about this more. Has there been any movement on this one?

@josephsl
Copy link
Collaborator

josephsl commented Oct 22, 2018 via email

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

@michaelDCurran michaelDCurran

Labels
enhancement feature/touch-screen
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@josephsl @michaelDCurran @nvaccessAuto @bhavyashah @Qchristensen