Unregister raw input device when DDIO shuts down #79
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
JeodC
pushed a commit
that referenced
this pull request
Apr 28, 2024
Unregister raw input device when DDIO shuts down
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.
This is to avoid problems with the mouse still being captured on an alt-tab.
One thing that I think should be resolved before any release is how mouse capturing will work. In windowed mode, the mouse cursor is shown, but it is still captured and exclusive to the window. Ideally, in windowed mode, the mouse should be visible and not captured when the game is in a UI. During this state, I think I can sync the software cursor with the actual hardware one, since legacy mouse events would be available.
When you're actually playing the game, however, the cursor should be invisible and captured to prevent it leaving.