dinput: the DIK_ keycode is not the same as the scancode.
aric at codeweavers.com
Thu Jul 31 12:30:46 CDT 2008
Here is a revised patch which builds the scancode->DIK table on
initialization making no xserver round trips required on lookup.
How does this look?
Aric Stewart wrote:
> Yes, I have verified those vkeys in windows.
> the VK_OEM_* keys are specificaly VK codes that vary from keyboard to
> keyboard. VK_OEM_3 is just one example.
> Vitaliy Margolen wrote:
>> Aric Stewart wrote:
>>> vkey codes similarly do not produce a clean 1 to 1 correspondance.
>>> the '@' key (0x1a) is vkey (VK_OEM_3) which is the vkey of the '`'
>>> key on the us keyboard.
>> This is needs to be fixed in x11drv then. Not in dinput. Have you
>> verified what v_keys you getting from windows for these keys?
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
More information about the wine-devel