Skip to content

Make Gestures bindings independent per button - #170

Open
asdolo wants to merge 1 commit into
mmaher88:masterfrom
asdolo:feat/per-button-gestures
Open

asdolo wants to merge 1 commit into
mmaher88:masterfrom
asdolo:feat/per-button-gestures

Conversation

@asdolo

@asdolo asdolo commented Oct 25, 2026

Copy link
Copy Markdown

Summary

  • Each button assigned Gestures keeps its own up/down/left/right/click map (Options+-style), instead of one shared profile-wide Gestures section.
  • Legacy flat [Gestures] profiles migrate by copying the shared map onto every gesture-trigger button.
  • Assigning Gestures to a button for the first time seeds that button from device defaultGestures.

Test plan

  • Assign Gestures to two buttons; change a direction on one — the other must stay unchanged
  • Restart app / reload profile — per-button bindings persist under [Gestures/<buttonIndex>/…]
  • Open an older profile with flat [Gestures] keys — both gesture buttons still work, then diverge after editing
  • logitune-tests filters for *Gesture*, ProfileEngine.*, DeviceModelTest.*Gesture* pass

Each gesture-trigger button keeps its own direction map (Options+-style)
instead of sharing one profile-wide Gestures section.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant