Path: utzoo!attcan!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!mailrus!ames!hc!lanl!opus!jthomas
From: jthomas@nmsu.edu (James Thomas)
Newsgroups: comp.windows.x
Subject: Re: events after an XWarpPointer
Message-ID: <JTHOMAS.89Apr26180625@bonito.nmsu.edu>
Date: 27 Apr 89 00:06:25 GMT
References: <JTHOMAS.89Apr26165411@tecate.nmsu.edu> <JTHOMAS.89Apr26174542@bonito.nmsu.edu>
Sender: news@nmsu.edu
Organization: NMSU Computer Science
Lines: 17
In-reply-to: jthomas@nmsu.edu's message of 26 Apr 89 23:45:42 GMT

In article <JTHOMAS.89Apr26174542@bonito.nmsu.edu> I too hurriedly write:

dummy> If I add an event handler for ButtonPress events to the second
dummy> widget, it does get called, but only when the button is released.
dummy> (Yes, I just looked at the code again, and unless the xxxMask
dummy> symbols are read-once/redefine-after-use, I have the routines
dummy> matched with the right event masks.)  ??

Sorry!  The event adds were right, but the routine names were swapped.
With the right routine names the whole thing worked OK.  Without the button
pressed handler, the leave window event is still generated on (the first?)
button press.

(Moral: include a button pressed event handler and take care before
posting.)

Jim Thomas   jthomas@nmsu.edu