Windows touch #1461
Merged
Windows touch #1461
Conversation
This file contains 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
…touch-specific logic: 1) force the rate to be 1:1; 2) in Windows, don't try to reset the cursor (via. SetCursorPos), which is usually done to avoid the mouse bumping up against the edge of the screen. These work together to allow touch to work as expected on Windows, while preserving existing mouse behavior.
|
Hey I reviewed and merged. Looks great. Can you fire in a separate PR to add yourself to the AUTHORS file? Format should be obvious. Thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
For windows, handle touch events differently from mouse events. Note this includes/requires an update to the vstgui subproject.