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
The latest version (v0.8.0) has much lower latency but there is a small issue: the NumLock / CapsLock keys are sent to the target PC but status leds on the keyboard are not updated. Checked with win and linux clients using Keychron K5 SE and iClever keyboards.
The text was updated successfully, but these errors were encountered:
Hey @ig-sinicyn
I've taken some time off :)
I just tested this and I couldn't reproduce this with my Cherry Keyboard, both Windows and Linux. Will try some more. @cylonid, you seem to have the same issue?
@quaxalber I do have the same issue on a Microsoft Surface keyboard, yes. Perhaps it is an issue with one of the included libs?
Regarding older versions:
I know that the LEDs used to work in principle. So they were not dead like they are in the current version.
However, I remember that at some point the lights were inverted. So the Numlock light was on when Numlock was actually off and vice versa. I cannot say if it was always the case or if that bug only occurred after playing around with Numlock, going into standby, wake up again etc., because the LED thing is not really an issue for me.
Hi!
The latest version (v0.8.0) has much lower latency but there is a small issue: the NumLock / CapsLock keys are sent to the target PC but status leds on the keyboard are not updated. Checked with win and linux clients using Keychron K5 SE and iClever keyboards.
The text was updated successfully, but these errors were encountered: