Hello,
We are having some problems with Synergy running on OpenSUSE Linux, such that the capslock key on the client is occasionally randomly toggling, rESultIng iN tYPIng lIKe tHis... We also have problems that Numlock is sometimes not working on the client.
To investigate this, I created a program that logs 'keydown' and 'keyup' events. I run this program on client and server.
When I have Capslock ON, and press/release key 'A' on the keyboard, I see this:
Server:
- Keydown, keycode 65, received char "A"
- Keyup, keycode 65, received char "A"
Client:
- Keydown, keycode 16777252
- Keyup, keycode 16777252 (these two codes basically set capslock on client to ON)
- Keydown, keycode 65, received character "A"
- Keydown, keycode 16777252
- Keyup, keycode 16777252 (these two codes basically set capslock on client back to OFF)
- Keyup, keycode 65, received character "a"
Note the difference on the final keyup-events for server and client. The server get a keyup for capital "A" (=ok), the client gets a keyup-event for lower-case "a" (=not OK??).
Depending on the application, this behavior may or may not impose a problem. Applications acting on 'keyup' will get the wrong character...
Now my question: Is the described behavior intended? Or is this a bug?
We're running Synergy 1.4.10, and have halfDuplexCapslock,NumLock,ScrollLock set to TRUE.
I know this won't solve our issues with capslock/numlock, so any suggestions in that respect are also welcome :-)
Thanks,
Jeroen
