Make KeyBindingContainer.Prioritised
work for positional input too
#5966
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.
RFC.
This change would allow to replace this game-side workaround with usage of
KeyBindingContainer.IsPrioritised
. The workaround in question is a blocker in resolving a game-side p0 issue (ppy/osu#24248 (comment)).More specifically, this change ensures that the game-side workaround can be replaced with
IsPrioritised
without regressing issues like ppy/osu#6026. The fail case is when a child of theKeyBindingContainer
is handling a plain input handler method likeOnMouseDown()
, and handles the positional input before theKeyBindingContainer
even has a chance to see it. This is covered in the added test cases.