AprilNEA / AprilNEA/OpenLogi

[Bug]: MiddleClick not Working on my MX Anywhere 3.

Open
#680 1 comment 0 reactions 0 assignees View on GitHub
needs: triage type: bug
Dominant language
Rust
Stars
21k
Forks
675
Avg merge
1d 6h
Merged PRs (30d)
180

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?

GUI (desktop app)

### OpenLogi version

v0.7.1

### Operating system

Windows

### OS version & architecture

Windows 11

### Device model

MX Anywhere 3

### How is the device connected?

Logi Bolt 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?

I see the option to change the MiddleClick, but no matter what I choose, nothing happens.

### Steps to reproduce

1. Connect MX Anywhere 3
2. Middle Click.

### Diagnostics report

```markdown
### OpenLogi Diagnostics

**App**
- OpenLogi (GUI): v0.7.1 (release)
- Agent: v0.7.1 (connected)
- IPC protocol: GUI 17 / agent 17
- Inventory: ready
- OS: Windows (x86_64)
- Locale: en-GB (UI: follow system)
- Accessibility: granted · Input hook: installed
- Launch at login: yes · Menu bar: no · Update check: on
- Running from: source build (dev)
- Config: schema 4 · 1 configured device(s) · thumbwheel 14

**Assets**
- Source: user cache · Index: loaded (210 models) · User cache: present
- Cache path: C:\Users\MarcLaberge\.local/share/openlogi\assets · Bundle assets: absent

**Devices (1)**
- MX Anywhere 3 — mouse (codename: MX Anywhere 3)
- Connection: Logi Unifying receiver · Online: yes · Battery: 90% (discharging, full)
- Capabilities: buttons=yes, pointer=yes, lighting=no
- Model: 3b025 (wpid: 4090, model-ids: b025/4090/0000, ext-model: 03)
- Transports: eQuad, BTLE
- Render: mx_anywhere_3 · Slot 1

**Receivers (1)**
- Unifying Receiver (VID 046d / PID c52b)
```

### `openlogi list` output

```text
Not sure how to run this.
```

### Logs

```shell
Not sure how to run this.
```

### 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 middle-click remapping failure on Windows 11 with an MX Anywhere 3 over a Logi Bolt or Unifying receiver, using the GUI and connected agent described in the diagnostics. Trace the GUI button-remapping path through the input hook, then verify that the selected middle-click action is emitted; the fix is complete when the configured action works and the existing remapping behavior remains intact.

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
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.