Open
Conversation
to prevent issues with Input Movement/activity while the Window isn't in focus: the ability to only have any input be active based on Window being focused has been added. this can be disabled on `pd.ini`
Author
|
I actually debated whenever or not to use |
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.
When Alt-Tabbing: there's a chance that the input activity continues to be active, this is relatively fine if using the Controller (but the camera might get "camera snap" as a result), but if using Mouse Input: there's a chance that while the Window isn't focus, and the mouse cursor started to hover: the camera movement can move, at worse: when you alt-tab back in: you might have to correct the movement yourself.
This becomes a bigger problem during work on #644, where the Gyro Movement still becomes active while the window isn't in focus. This PR will address this specific issue where the Input Device method will be temporarily paused when the Window is no longer in focus.
inputWindowFocuscan be disabled onpd.ini, and it'll worke exactly how it was before.