Aaron Optimizer Digulla wrote:
> I'm all for 2 until I read the remote part :-) And to make things worse,
> here are some more nasties:
>
> - The X window manager will try to "help" us by processing certain
> keys first (if you use KDE, you cannot use any global keys like
> Ctrl-F1 because KWM swallows them before any app sees them). OTOH,
> we can try to find out just how KWM does this and use the same
> technique to swallow these keys before KWM sees them :-)
>
> - Another problem is that plex86 can loose and get the focus while modifier
> keys are depressed. This can irritate the OS running in plex86 because
> it will expect that it receives a scan-code "Ctrl is pressed" before it
> finds "Ctrl-C" in the input stream (well, actually, the user will
> wonder why plex86 will modify all keystrokes with Ctrl when it's not
> pressed). The solution here is probably to ignore modifier keyup/down
> events but always generate synthetic modifier keyup/down events depending
> on the modifier field in the X event.
There is an XGrabKeyboard call, which I would imagine would be how
to solve the situation of only seeing part of the keystroke stream,
much the same way as grabbing the mouse solves not seeing all of
the button press/release events.
Perhaps it's possible to save/restore all the WM bindings during
our keyboard grab, and reset to a state without the special key sequences?
-Kevin
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Kevin Lawton [EMAIL PROTECTED]
MandrakeSoft, Inc. Plex86 developer
http://www.linux-mandrake.com/ http://www.plex86.org/
