There is some difference in the keyboard defs, though not much. The most interesting is this line, from the remote machine, with +keyboard: trace:keyboard:X11DRV_ToUnicode Found keycode 13 (0x D) trace:keyboard:X11DRV_MapVirtualKey MapVirtualKey wCode=0x43 wMapType=2 ... trace:keyboard:X11DRV_MapVirtualKey Found keycode 13 (0x D) trace:keyboard:X11DRV_MapVirtualKey returning 0x63. This is not found in the output of the local X server. I'm still looking at the copious output produced by both the +message log and the +relay log. There's substantial differences in them; but I'm not quite sure which differences are important. But I'm learning.... - Tony Ove Kaaven wrote: > > It's not always the keysyms that matter, but how Wine maps those keysyms > to Windows VK codes. Keyboard layout checking gets more verbose with > --debugmsg +keyboard,+key, though this is admittedly unlikely to be the > problem. I'd rather recommend --debugmsg +message or something if you > want to find app-visible differences in the input processing. > > Or else, you can of course do --debugmsg +relay and study the differences > between local and remote leading up to the messagebox with that, which > may pinpoint a likely culprit... > _______________________________________________ wine-users mailing list wine-users@winehq.com http://www.winehq.com/mailman/listinfo/wine-users
