Fix Windows 10 mouse issues#7
Open
XaserAcheron wants to merge 2 commits into
Open
Conversation
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.
Closes #6
This patch does two things (on two commits);
input/inputSDL.cppto the mouse capturing code and removes the manualCenterMouse()call, since this seems to have independently triggered the same Win10 compatibility issue SDL itself ran into.The 2nd fix more or less mirrors what newer Kex builds do (judging from what info I've been able to glean from Edward, at least :P), and it's been confirmed working by a few folks, so hopefully this is all kosher.
For the record, this is the exact same as the fix found here. I compiled that EXE from an early test branch. :P