>AFAIR (Alexandre can correct me if I am wrong),
I think we can make that an abbreviation too: ACCMIIAW
Will be widely used in almost every wine list posting :)
bye Fabi
On Tue, Oct 21, 2003 at 05:34:17PM +0200, Gerhard W. Gruber wrote:
> Don't we know this? And even if not, is there no way to forward the event to
> the normal event chain? In Windows there are Hookfunction and at some hooks
> you can choose to keep the event or continue it's processing. Is there no
On Tue, 21 Oct 2003 09:13:28 +0200, Lionel Ulmer <[EMAIL PROTECTED]> wrote:
>Well, this would work BUT there is a catch : when you grab the display
>or some keys, only the X connection where you did the grab will get the key
>events. And as in Wine, you have one connection per thread, you need
(snip about XGrab-ing stuff)
> I think that using this should work at least in programs where the entire
> screen is taken over, like in games, probably other applications well.
Well, this would work BUT there is a catch : when you grab the display
or some keys, only the X connection where yo
I currently write a small desktop app (in case you are curious
http://sourceforge.net/projects/launchmenu) and for this I have to research on
how to grab mouse events and eventually keyboard as well. Now I thought that
this might be usefull for wine when playing games under the DirectX emulation,
s
