Android: on-screen controls vs. system gestures #826
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
stale
wontfix
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gh-streetpea/chiaki-ng!826
Loading…
Reference in a new issue
No description provided.
Delete branch "aoleg94/android-fix-touch-cancel"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
left stick) takes the touch over with
ACTION_CANCEL. The controls only released onACTION_UP, so the stick, a button or a touchpad finger stayed held, even into the next session.TouchTracker(stick, d-pad),ButtonViewandTouchpadViewnow release on cancel.systemGestures()insets (back zones at the sides, home at the bottom) are meant for thesystem; the controls now ignore them.
Testing
TouchTrackerTest(cancel fails before the fix) andSystemGestureAreaTest.TouchTrackergained an overload taking action, pointer id and positions so it can be testedwithout
MotionEvent../gradlew testDebugUnitTestpasses.deflected; Back swipe from the left edge doesn't move the stick.
Notes
Developed with the assistance of Claude Code, and tested on real hardware as described above.
🤖 Generated with Claude Code
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.