fix: prevent unintended thumbwheel tap actions - #464
Open
mvanhorn wants to merge 1 commit into
Open
Conversation
Greptile SummaryThe PR separates thumbwheel rotation capture from tap delivery.
Confidence Score: 5/5The PR appears safe to merge. No blocking failure remains.
|
| Filename | Overview |
|---|---|
| crates/openlogi-agent-core/src/watchers/gesture.rs | Derives and tracks the typed thumbwheel capture mode from sensitivity and effective bindings. |
| crates/openlogi-hid/src/gesture.rs | Applies the typed mode during diversion and independently gates rotation and tap forwarding. |
| crates/openlogi-hid/src/gesture/tests.rs | Covers rotation-only, rotation-plus-tap, zero-motion, and native forwarding behavior. |
| crates/openlogi-hid/src/lib.rs | Re-exports the new thumbwheel capture-mode type. |
Sequence Diagram
sequenceDiagram
participant Config as Effective bindings
participant Watcher as Gesture watcher
participant HID as HID capture session
participant Device as Thumbwheel
participant Dispatch as Action dispatcher
Config->>Watcher: Sensitivity and click/rotation bindings
Watcher->>Watcher: Derive capture mode
Watcher->>HID: Start or restart session with mode
HID->>Device: Keep native or enable diverted reporting
Device-->>HID: Rotation and optional tap report
alt Diverted rotation only
HID->>Dispatch: Forward rotation
else Diverted rotation and tap
HID->>Dispatch: Forward tap and rotation
else Native
Device-->>Config: OS handles native reporting
end
Reviews (2): Last reviewed commit: "fix: prevent unintended thumbwheel tap a..." | Re-trigger Greptile
mvanhorn
force-pushed
the
fix/435-prevent-unintended-thumbwheel-tap
branch
from
July 26, 2026 20:58
06235ec to
0d4b9af
Compare
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.
Summary
Replace the watcher's single thumb-wheel armed flag with a typed capture mode that distinguishes native reporting, diverted rotation only, and diverted rotation with tap delivery; derive it from sensitivity plus the effective click and rotation bindings. Thread that mode through
run_capture_session, export it fromopenlogi-hid, and include it in the manager's desired/current session state so changing the thumb-wheel click binding restarts capture with the correct behavior. Keep rotation decoding and re-synthesis unchanged, but have the HID listener emitButtonPressed(Thumbwheel)only when the mode explicitly includes taps, preventing rotation inversion from activating the seeded App Exposé default.Why
On an MX Master 3S, swapping the horizontal thumb-wheel directions causes touching the wheel to launch App Exposé even though only rotation was edited. The current watcher diverts HID++ Thumbwheel feature
0x2150whenever either rotation binding differs from its default, and the diverted listener then forwards every reported single tap asButtonId::Thumbwheel. The effective binding map always seeds that button with App Exposé, so rotation-only customization unintentionally activates a dormant default tap action. This path remains present on currentmaster, and there are no open or previously closed cross-referenced PRs for the issue.Testing
ThumbwheelScrollUpandThumbwheelScrollDownwhile the thumb-wheel click remains at its seeded default; the watcher selects rotation-only capture, wheel rotation scrolls in the inverted direction, and a tap/touch report emits no App Exposé action.Thumbwheelselects rotation-plus-tap and continues to deliver exactly one button event alongside any nonzero rotation in the same HID++ report.Fixes #435
AI was used for assistance.