[Bug 2400] Issue with Delete when NumLock active

[Wine Bugs]

http://bugs.winehq.org/show_bug.cgi?id=2400





------- Additional Comments From lav(a)etersoft.ru  2006-26-03 04:04 -------
Created an attachment (id=2138)
 --> (http://bugs.winehq.org/attachment.cgi?id=2138&action=view)
WINEDEBUG=+file for remote X server

trace:key:GetKeyState key (0x12) -> 0
trace:key:GetKeyState key (0x10) -> 0
trace:key:GetKeyState key (0x11) -> 1
trace:key:GetKeyState key (0x11) -> 1
trace:key:X11DRV_KeyEvent type 3, window a00001, state 0x2010, keycode 0x006b
trace:key:X11DRV_KeyEvent state = 2010 nbyte = 0, status 0x1
trace:key:X11DRV_KeyEvent KeyRelease : keysym=0 (No Name), # of chars=0 / 0x00
/ ''
trace:key:EVENT_event_to_vkey e->keycode = 6b
trace:key:X11DRV_KeyEvent keycode 0x6b converted to vkey 0x12e
trace:key:X11DRV_KeyEvent bScan = 0x53.
trace:key:X11DRV_send_keyboard_input  wParam=002e, lParam=c1530001,
InputKeyState=40
trace:key:X11DRV_KeyEvent type 2, window a00001, state 0x2010, keycode 0x006b
trace:key:X11DRV_KeyEvent state = 2010 nbyte = 1, status 0x4
trace:key:X11DRV_KeyEvent KeyPress : keysym=FFFF (Delete), # of chars=1 / 0x7f
/ '.'
trace:key:EVENT_event_to_vkey e->keycode = 6b
trace:key:X11DRV_KeyEvent keycode 0x6b converted to vkey 0x12e
trace:key:X11DRV_KeyEvent bScan = 0x53.
trace:key:X11DRV_send_keyboard_input  wParam=002e, lParam=01530001,
InputKeyState=c1
trace:key:TranslateMessage Translating key VK_DELETE (002e), scancode 53
trace:key:GetKeyboardState (0x4042f630)
trace:key:X11DRV_ToUnicodeEx (002E, 0153) : faked state = 0x2010
trace:key:EVENT_event_to_vkey e->keycode = 5b
trace:key:X11DRV_ToUnicodeEx type 2, window a00001, state 0x2010, keycode
0x005b
trace:key:X11DRV_ToUnicodeEx Translating char 0x2c to unicode
trace:key:X11DRV_ToUnicodeEx ToUnicode about to return 1 with char 2c
trace:key:TranslateMessage 1 -> PostMessageW(0x10026,WM_CHAR,002c,01530001)
trace:key:GetKeyState key (0x12) -> 0


-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.