-
-
Notifications
You must be signed in to change notification settings - Fork 769
Add touchpad gesture support for Windows Precision Touchpads #19823
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
Closed
Closed
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
8450e0d
Add WinAPI bindings for raw input
gexgd0419 0064a0c
Add touchpadHandler and make it start with core
gexgd0419 aad0f58
Lock the mouse when touchpad is being touched
gexgd0419 3b6ffbc
Set default gestures for touchpad
gexgd0419 6bdd252
Pre-commit auto-fix
pre-commit-ci[bot] File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd recommend to use only 1 category, since most of the touch scripts are common to touch screen and touch pad.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well after looking better to your code, I realize that all scripts are duplicated. So having 2 categories for them is OK if you keep them duplicated.
But I wonder if it wouldn't be worth factorizing touch screen and touch pad scripts, since these are very similar. I have not looked at it in depth tough.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's an interesting idea.
However, I'm not sure whether NV Access is willing to accept this into the core.
In order to prevent gesture conflicts, the system's built-in touchpad gestures should be disabled first. If the user does this manually in Settings, it will take effect immediately. However, if NVDA tries to modify the registry key, the change won't take effect until explorer restarts.
I found that in order to apply the changes, an undocumented interface has to be used to inform explorer of the changes. Undocumented interfaces can be unstable, which is why I'd like NV Access to make a decision here (see discussion). Without this undocumented interface, it's required to either restart explorer or instruct users to change the settings manually.