Fix overzealous pressed widget check#3605
Merged
AaronVanGeffen merged 2 commits intoOpenLoco:masterfrom Jan 14, 2026
Merged
Conversation
615b17d to
6b19431
Compare
duncanspumpkin
approved these changes
Jan 14, 2026
6b19431 to
2aa320f
Compare
6b19431 to
2aa320f
Compare
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
2 participants
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.
Dropdown widgets are not presented in their expected 'pressed' state when clicked. This has to do with
MouseInput::isPressedquerying the current input state, while thestateWidgetPressedfunction immediately resets this when handling the event.I believe
MouseInput::isPressedis overzealous in its checks, and so I've opted to remove the input state check.Before:
After:
