You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
when using my azerty Wooting Two HE, all keys detect normally thanks to scancode but the activation color remains red for keys that are different between qwerty/azerty no matter how far down they're pressed.
Example video (1.5 actuation) : https://streamable.com/mselx0
Note : I can't rename the keys because of a separate issue, the WA keys correspond to WA on the qwerty layout, so ZQ on azerty
The text was updated successfully, but these errors were encountered:
Ahh yes I was worried about this since I use two libraries (Wooting SDK + Keyboard hook) to capture keys and I have a file linking them together. Probably will have to create a switch for keyboard type. Will see what I can do!
when using my azerty Wooting Two HE, all keys detect normally thanks to scancode but the activation color remains red for keys that are different between qwerty/azerty no matter how far down they're pressed.
Example video (1.5 actuation) : https://streamable.com/mselx0
Note : I can't rename the keys because of a separate issue, the WA keys correspond to WA on the qwerty layout, so ZQ on azerty
The text was updated successfully, but these errors were encountered: