AprilNEA / AprilNEA/OpenLogi

[Bug]: Volume gesture only changes volume by one step

Open
#365 2 comments 3 reactions 0 assignees View on GitHub
needs: triage platform: windows type: bug
Dominant language
Rust
Stars
21k
Forks
675
Avg merge
2d 5h
Merged PRs (30d)
172

Description

### Pre-flight checklist

- [x] I searched [existing issues](https://github.com/AprilNEA/OpenLogi/issues?q=is%3Aissue) and this is not a duplicate.
- [x] I am on the [latest release](https://github.com/AprilNEA/OpenLogi/releases/latest) or a recent `master` build.
- [x] I quit **Logi Options+** before running OpenLogi (the two apps fight over HID++ access and only one can own a receiver at a time).

### Which part of OpenLogi?

Not sure

### OpenLogi version

0.6.19

### Operating system

Windows

### OS version & architecture

Windows 11 25H2 26200.8655

### Device model

MX Master 3S

### How is the device connected?

Bluetooth (direct, no receiver)

### Affected area(s)

- [ ] Device discovery / detection
- [x] Button remapping
- [ ] DPI control
- [ ] SmartShift
- [ ] Per-application profiles
- [ ] Battery status
- [ ] Settings / configuration (TOML)
- [ ] Auto-update
- [ ] Menu bar / tray
- [ ] Other

### What happened?

Setting my gesture button to Volume Up on Up direction, I would expect the volume to change continuosly while I'm moving the mouse up. Instead the volume changes one step and then doesn't change again.

### Steps to reproduce

1. Set any gesture to Volume Up (or Volume Down)
2. Perform the gesture
3. Volume changes one step
4. Keep performing the gesture
5. Volume no longer changes

### Diagnostics report

```markdown

```

### `openlogi list` output

```text

```

### Logs

```shell

```

### macOS permissions (if applicable)

- [ ] OpenLogi has **Accessibility** permission (needed to remap buttons via the event tap).
- [ ] OpenLogi has **Input Monitoring** permission (needed for Bluetooth-direct devices and capture).

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the gesture-button Volume Up and Volume Down behavior on Windows with an MX Master 3S connected over Bluetooth, then trace how repeated gestures dispatch volume changes. Done means each repeated gesture changes the system volume by one step instead of stopping after the first change.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
desktop
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
58/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.