8000 Fix the Lachesis button mappings. by zelch · Pull Request #117 · mbuesch/razer · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Fix the Lachesis button mappings. #117

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Conversation

zelch
Copy link
@zelch zelch commented Apr 22, 2018

Both the physical and logic button mappings seem to be wrong, at least for my Lachesis Classic.

These two commits fix both issues.

Without it, my side buttons end up getting mapped to profile changes instead of mouse buttons, which is less useful than it could be.

Zephaniah E. Loss-Cutler-Hull added 2 commits April 22, 2018 06:12
On the Lachesis, the profile and windows button definitions are swapped around
in two ways.

Profile switch up is 0x1A instead of 0xB.
Profile switch down is 0x1B instead of 0xA.
Windows button 4 is 0xA instead of 0x1B.
Windows button 5 is 0xB instead of 0x1A.

So not only are profile and windows button swapped on which has bit 5 set, but
the two buttons swap which is first in both cases as well.
The side buttons were backwards, with the left and right swapped.
@mbuesch
Copy link
Owner
mbuesch commented Aug 8, 2018

Thanks for your pull request.
To be able to pull this we would need to do this workaround in a way that does not break old devices with the old mapping. Maybe there is some way to detect, if the new mapping style is required? Firmware version perhaps?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0