http://bugs.winehq.org/show_bug.cgi?id=12939
--- Comment #16 from Harald Judt h.judt@gmx.at 2008-12-20 17:17:24 --- (In reply to comment #14)
No you can't do that. Wine _have to_ know and use the exact key state. If something sent key_down, key_up events to Wine that's the state Wine will have.
Ok, so I guess this behaviour has been changed in >=wine-0.9.59.
Also that state better match to all other X-events Wine receives. In your case
- it doesn't.
File bug with x-org. It should send consistent key states. Also you can't use trigger buttons (caps lock) for something that is not a trigger (control).
I would like to, but I'm a bit lost now. What exactly is X sending incorrectly and what should it send instead? It actually wouldn't help in my case, since caps_lock is just a trigger?
Remember the way key7board works in windows is different from the way it works
in X.
I remember you can change keyboard scan code mapping by editing the registry (search terms "caps_lock control registry"), and tried this but could not get it to work in wine. I guess this is not yet implemented, should I file a separate bug asking for enhancement?
Thanks for your explanation, it helped me solve another problem I had with Caps_Lock and imwheel in firefox but did not notice before. I've configured Caps_Lock to keep it's keysym but act as a control modifier, because this works and I believe that's the clearest way to deal with this.