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
kbct seems to always pick event4 and the last one wins, but the one that actually receives the key events is on /dev/input/event2.
I made a patch to work around this by checking if there is already a keyboard with the current name in the device map, and if so, append the device number to the end. So after the patch, the second one becomes RDR Rainy 75-4, and I can stick RDR Rainy 75 in the list of keyboards and it works.
I will push a PR shortly.
The text was updated successfully, but these errors were encountered:
mschout
added a commit
to mschout/kbct
that referenced
this issue
May 22, 2024
I have a new keyboard (Wobkey Rainy 75) that, when in wired mode, exposes itself with the exact same name on multiple device paths:
e.g.:
kbct
seems to always pickevent4
and the last one wins, but the one that actually receives the key events is on/dev/input/event2
.I made a patch to work around this by checking if there is already a keyboard with the current name in the device map, and if so, append the device number to the end. So after the patch, the second one becomes
RDR Rainy 75-4
, and I can stickRDR Rainy 75
in the list of keyboards and it works.I will push a PR shortly.
The text was updated successfully, but these errors were encountered: