Fix SetCursorPos and ClipCursor ignoring DPI awareness #1394
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.
This fixes the issue of
SetCursorPos
coordinates being scaled incorrectly when high-DPI display scaling is active. (#1369)The
DPI_AWARENESS_CONTEXT
of the calling thread is passed to GuiServer, which is applied there before calling the actual WinAPI. The originalDPI_AWARENESS_CONTEXT
of the GuiServer thread is then restored immediately to prevent affecting other functions.The same fix has been applied to
ClipCursor
,but I do not have a way to test it.SendInput
doesn't seem to be affect by the looks of it. I have not checked the other APIs.