wine users - Jun 2001 - X11: Oracle Forms runs fine locally, but not remotely

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...
>

Tony <tony@searhc.org> wrote:
> 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....
Good ! It's important to be persistent in Wine debugging...

In case of questions, http://search.microsoft.com/default.asp
might be a useful site.

-- 
Andreas Mohr, Renningen, Germany
In case you need to contact me after expiry of temporary email address:
my real address is (initial of first name).(last name)@mailto.de

Tony <tony@searhc.org> writes:
> 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.
That's a hit of the "C" key, which yields the ASCII character
"c".

Okay, making *some* progress.  I still don't grok the X11 code, nor all 
the debug output.  However, I'm slowly getting used to looking at it.

This is the interesting bit from the output of
       --debugmsg +key,+keyboard,+relay


-------------
Local:

08067eb0:Call 
x11drv.ToUnicode(0000000d,0000001c,40739e40,405b5f3c,00000002,00000000) 
ret=406e7cb5
trace:key:X11DRV_ToUnicode (000D, 001C) : faked state = 0
trace:keyboard:X11DRV_ToUnicode Found keycode 36 (0x24)

Remote:

08067eb0:Call 
x11drv.ToUnicode(0000000d,0000001c,40739e40,405b5f3c,00000002,00000000) 
ret=406e7cb5
trace:key:X11DRV_ToUnicode (000D, 001C) : faked state = 0
trace:keyboard:X11DRV_ToUnicode Found keycode 47 (0x2F)

--------------

This is the critical spot where "return" is hit to submit the request;
on the local display, everything works perfectly.  On the remote, it 
doesn't.

I'm hopeful this is the spot; I'm looking it up in the source code as we
speak, but (as I said) I don't quite get it all yet.  Am I on the right 
track?  If so, any suggestions on subtleties I should know about?

Thank you for your help so far.

			- Tony