[Bug]: Portable Install stores data under users folder in 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?
Not sure
### OpenLogi version
0.8.1
### Operating system
Windows
### OS version & architecture
Windows 11 x64
### Device model
Mx Master 3S
### How is the device connected?
Logi Bolt receiver
### Affected area(s)
- [ ] Device discovery / detection
- [ ] Button remapping
- [ ] DPI control
- [ ] SmartShift
- [ ] Per-application profiles
- [ ] Battery status
- [x] Settings / configuration (TOML)
- [ ] Auto-update
- [ ] Menu bar / tray
- [ ] Other
### What happened?
When running OpenLogi, data seems to be stored in the users folder, IE, `C:\Users\USERS_NAME_HERE\.config\openlogi`, instead when running from a portable version, it should be configurable, or ideally store in the same place as the exe is running from.
### Steps to reproduce
1. Download a portable(zip) build of openlogi
2. Run it
3. Confirm settings are stored in user specific folder
### 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 issue with the portable ZIP build on Windows 11 and inspect how the OpenLogi settings/TOML location is selected. Confirm the current user-folder behavior, then verify that the chosen portable storage behavior is configurable or uses the executable's directory.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100