Once again: YDKJ

[Stefan Leichter]

Andreas Mohr Usenet 07/01 wrote:
> 
> Try running with --debugmsg +relay,+msg,+message,+event,+dinput,+key,+keyboard.
> That should clue you in on the problem.
> (check whether events from +event get through to the app/msg processing layer)

Hello,

comparing the traces of wine-20000613 and wine-20010731 i found a
difference when pressing e.g. the key '1': 

the old (working) version generates the events:
1.) WM_KEYDOWN
2.) WM_CHAR
3.) WM_KEYUP

the new (failing) version generates the events (see below):

1.) WM_SYSKEYDOWN
2.) WM_SYSCHAR
3.) WM_SYSKEYUP

Could this be the reason for the problem?

Bye Stefan
-------------- next part --------------
trace:event:EVENT_ProcessEvent called.
trace:event:EVENT_ProcessEvent Got event KeyRelease for hwnd 013c
trace:key:X11DRV_KEYBOARD_HandleEvent state = 0
trace:key:X11DRV_KEYBOARD_HandleEvent KeyRelease : keysym=31 (1), ascii chars=1 / 31 / '1'
trace:key:X11DRV_KEYBOARD_HandleEvent keycode 0xa converted to vkey 0x31
trace:key:X11DRV_KEYBOARD_HandleEvent bScan = 0x02.
trace:event:KEYBOARD_SendEvent (49,2,0002)
trace:key:queue_kbd_event  wParam=0031, lParam=c0020001, InputKeyState=1
trace:event:EVENT_ProcessEvent returns.
0806b700:Ret  x11drv.MsgWaitForMultipleObjectsEx() retval=00000000 ret=40773545
trace:msg:peek_message got hwnd 13c msg 104 (WM_SYSKEYDOWN) wp 31 lp 20001
0806b700:Ret  user32.PeekMessageA() retval=00000001 ret=0040382c