tests: cover the win32 backend mouse location#154
Open
DTW-Thalion wants to merge 1 commit into
Open
Conversation
Adds a test for the win32 display server -mouselocation and -mouseLocationOnScreen:window:. The cursor is moved to two known screen positions and the reported location is checked: moving it right increases the reported x by the same amount, moving it down decreases the reported y because the win32 top-left origin is flipped to the GS bottom-left origin, and -mouseLocationOnScreen:window: reports the same point as -mouselocation. The cursor is restored afterwards. It builds only for the win32+cairo backend and skips when the backend cannot be reached, so it is inert on the other backends and in CI.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Adds a test for the win32 display server -mouselocation and
-mouseLocationOnScreen:window:.
The cursor is moved to two known screen positions and the reported location is
checked: moving it right increases the reported x by the same amount, moving it
down decreases the reported y because the win32 top-left origin is flipped to
the GS bottom-left origin, and -mouseLocationOnScreen:window: reports the same
point as -mouselocation. The cursor is restored afterwards.
It builds only for the win32+cairo backend and skips when the backend cannot be
reached, so it is inert on the other backends and in CI.