I have problems with the keys 91 and 93 (the square brackets keys on the US keyboard). These are being wrongly mapped on the client side (as reported here).
I recently noticed in DEBUG1 output that any single key click (key down key up) on these keys produces twice key up and twice key down events on the client while other always have one down and one up as expected:
DEBUG1: recv key down id=0x0000005b, mask=0x2000, button=0x001a
DEBUG1: mapKey 005b (91) with mask 2000, start state: 0000
DEBUG1: find best: 0000 2000
DEBUG1: best key index 0 of 2 (exact)
DEBUG1: found key in group 0
DEBUG1: state: 0000,0020,0021
DEBUG1: flip: 0020 (0000 vs 0020 in 0021 - 0000)
DEBUG1: desired state: 2000 0020,0020,0021
DEBUG1: flip: 0000 (0020 vs 2000 in ffde - 6020)
DEBUG1: mapped to 011, new state 0000
DEBUG1: keystrokes:
DEBUG1: 05c (00000000) down
DEBUG1: 011 (00000000) down
DEBUG1: 05c (00000000) up
[DEBUG1: recv key up id=0x0000005b, mask=0x2000, button=0x001a
DEBUG1: keystrokes:
DEBUG1: 011 (00000000) up
Maybe it is really a bug. What do you think?
asked
23 Jul '12, 07:14
Daniel Tkatch
61●2
accept rate:
0%
In that log snippet, I actually can't see the 2 key up or down events that you mention. There is 1 "recv key down" and 1 "recv key up" -- and I'm a bit suspicious of that square bracket on the 3rd line from the bottom.