Add option to configure mouse bindings #5022
Merged
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.
The argument must be exactly 4 characters, one for each secondary click:
Each character must be one of the following:
+
: forward the click to the device-
: ignore the clickb
: trigger shortcut BACK (or turn screen on if off)h
: trigger shortcut HOMEs
: trigger shortcut APP_SWITCHn
: trigger shortcut "expand notification panel"For example:
This deprecates
--forward-all-clicks
(use--mouse-bind=++++
instead).Refs #2258 (comment)
Also forward all clicks by default for UHID/AOA
By default, only the left click is forwarded to the device, and secondary clicks trigger shortcuts (the behavior can now be configured by
--mouse-bind=xxxx
).But when the mouse mode is relative (AOA and UHID modes), forward all clicks by default. This makes more sense since the cursor is handled on the device side, the user expects all mouse buttons to be forwarded.
Refs #4727 (comment)
Supersedes #4877