http://bugs.winehq.org/show_bug.cgi?id=12939
Harald Judt h.judt@gmx.at changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |UNCONFIRMED Resolution|INVALID |
--- Comment #12 from Harald Judt h.judt@gmx.at 2008-12-20 12:41:50 --- (In reply to comment #10)
There are still something external to Wine running that messing with key states. The telltale sign are these lines:
[...]
Which mean that after you pressed control key, Wine processed it, then checks it's state as reported by the system. That state is reported as depressed and Wine readjusts it. So all you see is just a single "click" on the control key.
Thanks for your explanation.
I found out this has to do with the way I configure my Caps_Lock and Control keys. If I use the standard configuration (Caps_Lock as Caps_Lock), then everything is fine and Control_L works as expected in WINE.
This bug is invalid. You have something in your system that messing with reported key states to Wine. This can not be fixed by Wine.
I have to argue. I WANT to use both Caps_Lock and Control_L as control keys. In every other application, this works as expected, just not in wine. There is no external program messing with key states.
You don't even need to configure anything else, just add the following commands to your .Xmodmap or use xmodmap -e "<command>":
remove Lock = Caps_Lock keysym Caps_Lock = Control_L add Control = Control_L
So WINE simply does not respect my X keyboard configuration. I can use Caps_Lock as Control_L (which is what I do most of the time), but then the real Control_L will not function as Control_L in WINE. This is wrong, and this is why I reported this bug.
Closing invalid.
Please see my initial posting. This worked in <wine-0.9.59. Why doesn't it work now?