Path: utzoo!attcan!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!husc6!frooz!cfa250!mvh
From: mvh@cfa250.harvard.edu (Mike Van Hilst)
Newsgroups: comp.windows.x
Subject: XCheckWindowEvent with ButtonMotionMask
Keywords: event
Message-ID: <1587@cfa241.cfa250.harvard.edu>
Date: 2 Jul 89 06:12:37 GMT
Distribution: na
Organization: Harvard/Smithsonian Center for Astrophysics
Lines: 21

Simply put: when a window has PointerMotionMask in its event mask,
XCheckWindowEvent(.., ButtonMotionMask, ) returns all MotionNotify
events, including those after the Button was released.

I am using the MIT XV1R3.  The problem is easy to demonstrate in dbx.
Stop after the XNextEvent got the ButtonPress and before the afore
mentioned call in a while loop.  Release the button, move the pointer
off the window and do "cont".

I have an application which involves a lot of pointer tracking
(drawing graphics, changing colors, magnifying the area of interest,
displaying the pointer coordinates).  In some situations the pointer
is tracked, button or no.  In other situations, the pointer is only
tracked with a button down.

Is this a bug which will be fixed in the next release, or does it
reflect a design philosophy?

Meanwhile, yes, I am going to use XCheckIfEvent().

	Mike VanHilst