[Bug]: Remapped MX Master 3S buttons do not work in VMware on Windows
- 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?
GUI (desktop app)
### OpenLogi version
0.8.1
### Operating system
Windows
### OS version & architecture
win11
### Device model
MX master3s
### 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?
The mouse functions in vmware are not available, such as win+table functions, and the mouse is not available for switching tabs in the browser. Operations on the edge interface of the vmware software are also ineffective. (openlogi is installed on the windows physical machine, but is not installed in vmware.)
### Steps to reproduce
1. Install openlogi on a windows physical machine
2. Install windows in vmware (without installing openlogi)
3. Press the mouse in vmware/or press the mouse (win+table) in the vmware software interface
### 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
Reproduce the button-remapping failure with OpenLogi on a Windows host running VMware, using the MX Master 3S with a Logi Bolt receiver. Start by tracing the GUI's button-remapping and input handling paths; done means remapped buttons work inside VMware, including tab switching and VMware edge-interface controls.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100