It seems to be 'OK' for X11 to return that because everyone in the X11
universe seems to just accept that as how X works. Not fixing it wine
would mean require all wine users to use something like xmodmap to
modify their own xservers to get the correct behavior.
That doesn't seem like an
Aric Stewart a...@codeweavers.com wrote:
It seems to be 'OK' for X11 to return that because everyone in the X11
universe seems to just accept that as how X works.
Could you please provide an example of this? How other projetcs cope with
that?
Having an appropriate X11 keyboard layout
Dmitry Timoshkov wrote:
Aric Stewart a...@codeweavers.com wrote:
It seems to be 'OK' for X11 to return that because everyone in the X11
universe seems to just accept that as how X works.
Could you please provide an example of this? How other projetcs cope with
that?
Having an appropriate
A bug made itself present in VkKeyScan's handling of the less-than
character on US (and other) keyboard layouts. VkKeyScan('') in Windows
returns 0x1bc, which is VK_OEM_COMMA with the shift key flag set. In
Wine, VkKeyScan('') returns 0xe2, which is VK_OEM_102, or the VK for
the infamous
Andrew Eikum wrote:
A bug made itself present in VkKeyScan's handling of the less-than
character on US (and other) keyboard layouts. VkKeyScan('') in Windows
returns 0x1bc, which is VK_OEM_COMMA with the shift key flag set. In
Wine, VkKeyScan('') returns 0xe2, which is VK_OEM_102, or the VK
Andrew Eikum aei...@codeweavers.com wrote:
The root cause of this is X's XKeysymToKeycode returning the keycode for
the phantom key instead of the keycode for the comma key when passed the
keysym for '' (XK_less). This isn't incorrect on X's part, but
inconvenient for Wine as most US
