Pass xrel/yrel if SDL relative mouse mode is enabled#282
Closed
oznogon wants to merge 1 commit into
Closed
Conversation
Owner
|
This is just weird abuse of interfaces. The onPointer functions expect screen coordinates and not relative movements. If we want relative movements we should just have a new interface for that. |
This was referenced Dec 18, 2025
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
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.
If SDL relative mouse mode is enabled, SP doesn't send the xrel/yrel delta values it generates and shouldn't map those values to pixel coords. Detect if relative mouse mode is enabled and pass the expected values.
Prereq for captured mouselook in Cinematic View without redundantly calculating mouse movement deltas from pixel coords and preventing the cursor from escaping the window.