http://bugs.winehq.org/show_bug.cgi?id=8683
Fábio Capela fabio.capela@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #10365|0 |1 is obsolete| |
--- Comment #13 from Fábio Capela fabio.capela@yahoo.com 2008-01-20 11:54:08 --- Created an attachment (id=10382) --> (http://bugs.winehq.org/attachment.cgi?id=10382) Hack to make almost all keys from DE layout work in WoW
(In reply to comment #12)
Thanks for finding the reason of the bug. Now we just need to figure out a proper fix for this. Do you know which vkey values WoW tries to convert to characters and that fail?
Something strange, today no keys are returning 0 for me, they are returning 0xffffff?? (which makes my first hack not usefull) and still don't work under WoW.
Testing right now, with "setxkbmap de", listing the key face on my US keyboard, what it produces with de DE layout, it's numeric virtual key, the virtual key name and the result from MapVirtualKeyEx for the keys that don't work on WoW:
<-> ß 189 VK_OEM_MINUS 0xffffffe1 <=> ' 187 VK_OEM_PLUS 0xffffffc2 <[> ü 219 VK_OEM_4 0xffffffc3 <;> ö 186 VK_OEM_1 0xffffffc3 <'> ä 222 VK_OEM_7 0xffffffc3
(With this keyboard layout the <=> key also triggers the deadkey bug I described before.)
The VKs are exactly the same produced by those same keys under the US keyboard layout, under which this problem don't happens in WoW.
With "setxkbmap de -variant nodeadkeys" the <=> key works, producing a different result: <=> ' 224 VK_??? 0x27
This new hack makes all keys except from <'> from the DE layout work, and all keys from de DE layout without dead keys, work, at least in my install. (As a collateral effect the key shown on the keybindings list is the corresponding key in the US keyboard, but it works.)