Repository navigation
Share keyboard and gamepad axis adjustments - #187
Merged
Merged
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
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.
Why
SplitPaneandScrollbarindependently translated the same Home/End, main-axis arrows, gamepad navigation and activation events into requested values. Adding an adjustment gesture required updating both dispatchers.Change
One private input helper interprets those events. Both callers retain their existing numeric precision, bounds, focus requirements, drag lifecycle and semantic action dispatch. Public API compatibility is preserved.
Validation
split_pane,scrollbarand the window-freeinspector_hierarchysmoke.git diff --checkpassed.