Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!ucbvax!bloom-beacon!dont-send-mail-to-path-lines
From: mouse@lightning.mcrcim.mcgill.EDU (der Mouse)
Newsgroups: comp.windows.x
Subject: Re: OpenWindows button events question
Message-ID: <9104130056.AA08365@lightning.McRCIM.McGill.EDU>
Date: 13 Apr 91 00:56:05 GMT
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 25

>> This strikes me as a bad way of doing things.  It means that your
>> application does not have the automatic passive grab you normally
>> would for a button press,
> Nope.  The semantics of AllowEvents(ReplayPointer) are that windows
> further down in the hierarchy can also have passive grabs activated.

The order of the ButtonPress and EnterNotify events implies that the
reprocessing is happening before olwm's grab is being released.  Does
this then imply that there can be two pointer grabs active at once?
(The not-yet-released WM grab and the client's grab, either explicit or
by default on a button press).  Surely not.

>> and it also generates this strange sequence of events implying the
>> mouse is not in the window when the press happens.
> The sequence if events is indeed strange.  As you mention above,
> there is enough information in the events for the program to
> disambiguate them.

This is a lesser complaint; that's why I put it second.  As you say,
it's not serious, but it really shouldn't be necessary.

					der Mouse

			old: mcgill-vision!mouse
			new: mouse@larry.mcrcim.mcgill.edu