Fix set navigation: double-click from Set 3 goes to Set 2

87841b2be3493be896dc8478680312c005680ae4 · Claude · Jan 22, 2026 20:35

Previously, double-click from Set 3 went to Set 1, which was
inconsistent and confusing because both double-click and triple-click
from Set 3 did the same thing.

New behavior:
- Set 1 → double-click → Set 2
- Set 2 → double-click → Set 1
- Set 3 → double-click → Set 2 (changed from Set 1)

- Set 1 → triple-click → Set 3
- Set 2 → triple-click → Set 3
- Set 3 → triple-click → Set 1

This is more intuitive because:
1. Double-click is for the "primary" sets (1 ↔ 2)
2. Triple-click is for accessing the "special" Set 3
3. From Set 3, you have two escape routes:
   - Double-click → Set 2 (quick return to primary sets)
   - Triple-click → Set 1 (back to start)

Files modified:
- src/device.c: Change Set 3 double-click target from Set 1 to Set 2

+2 −2 · 1 file changed

src/device.c +2 −2

diff --git a/src/device.c b/src/device.c
index eb140df..d2cd5eb 100644
--- a/src/device.c
+++ b/src/device.c
@@ -332,8 +332,8 @@ void device_run(libusb_context* ctx, config_t* config, int debug, int accept, in
                                 } else if (wheel_current_set == 1) {
                                     wheel_current_set = 0;
                                 } else {
-                                    // From Set 2, go to Set 0
-                                    wheel_current_set = 0;
+                                    // From Set 2, go to Set 1 (not Set 0)
+                                    wheel_current_set = 1;
                                 }
                                 wheel_position_in_set = 0;  // Start at first function in new set
                             } else if (final_click_count >= 3) {