Closed stevegolton closed 2 years ago
Egg-on-face moment. Turns out there already exists a solution for this. Enabling "Onboard Profiles" did the trick - see the screenshot below. Note: This requires solaar version 1.1.2
It's good that you found a solution, but the behaviour you describe is weird.
What Solaar did is turn off (Disable) your mouse's onboard profiles, which is a complex feature that reprograms the mouse based on information stored in the mouse that can be modified by software. Why onboard profiles should flip the forward and back buttons is a mystery to me.
What used to happen is that Solaar disabled onboard profiles to change the report rate. I expect that you set this feature to 'ignore' because otherwise the back and forward buttons would have flipped. With version 1.1.2 onboard profiles is a separate setting (because there are now two settings that may need it to be disabled).
The only remaining question is why Solaar 1.1.2 wanted to disable onboard profiles. What might have happened is that an older version of Solaar was running without report rate set to ignore (and thus it disabled onboard profiles) and that is the setting value that Solaar 1.1.2 picked up.
Thank you very much for the information @pfps.
I can confirm if I set the polling rate to ignored in solaar v1.1.1 and restart the mouse, the side buttons return to the correct orientation. Indeed, it seems that solaar doesn't try to enable onboard profiles with this setting set to ignored. I haven't tried this with solaar v1.1.2.
As to why solaar 1.1.2 wanted to disable onboard profiles, I think your suspicions are correct seeing as I was using v1.1.1 for a while and had tinkered around with just about every setting possible for this mouse before I tried v1.1.2.
Information
solaar 1.1.2
|1.1.2-2-g8e7435e
solaar show
for the target device (if applicable):Is your feature request related to a problem? Please describe. Before I start solaar, my G603 mouse's side buttons operate correctly as "forward" and "back" actions in apps like firefox, nautilus, and vscode. By "correctly" I mean the front button corresponds to forward, and the rear button corresponds to back. Using
xev
I can see that the front button is recognized as button 9 and the rear button is button 8.When I start solaar, these buttons become swapped. The front button becomes button 8 and the rear button becomes button 9. Thus, the front button operates as "back" and the rear button operates as "forward" in the aforementioned apps. This persists until I quit solaar and turn my mouse off and on using the power switch.
Perhaps on startup solaar is setting some register on the mouse which flips this setting?
Describe the solution you'd like I would like a way to switch these buttons back to their default functionality in solaar. I'm not sure what form this setting would take, as I don't know how these buttons are getting switched in the first place. Either a toggle switch called "Swap side buttons", or the ability to remap the buttons would be ideal. The solution will depend on what registers/options are supported by the mouse.
Describe alternatives you've considered I only actually need solaar to take control of my keyboard and I don't use any of it's features for the G603 mouse, it's just picked up automatically. So an alternative solution would be to blacklist the mouse and leave it alone, but I'm not sure if that's possible with solaar.
Additional context I'm happy to look into this, but I have no idea where to start debugging HID++ registers in order to work out how to proceed, so a pointer in the right direction would be awesome!