Fixes mouse coordinates for Windows when display is set to a higher DPI #7362
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
…PI (ex: enlarged by 150% using display settings)
|
👍 |
|
@bsclifton @zcbenz I think this has broken mouse position inside a My app currently has an issue where the mouse point would stutter all over the place in a webview (seemingly in multiple places at once) If you read this issue thread from this comment down MarshallOfSound/Google-Play-Music-Desktop-Player-UNOFFICIAL-#1777 (comment) You can see that users disabling display scaling fix the issue. This PR seems to correspond with the version jump that caused the issue. Any thoughts on whether this is the cause? |
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.
Fixes mouse coordinates for Windows when display is set to a higher DPI (ex: enlarged by 150% using display settings)
Draggability was being impacted when display settings were bumped up. The wrong coordinates would be considered for the hit testing.
Fixes #7347