[winGRASS] libG11

[Malcolm Blue]

> -----Original Message-----
> From: Glynn Clements [mailto:glynn.clements at virgin.net]

> >
> > Well, that's the problem then.  I only discarded the event I was looking
> > for. So we should flush the queue while checking.
>
> More precisely, events shouldn't be queued unless they are enabled by
> the window's event mask (certain events, e.g. ClientMessage, don't
> have a corresponding bit in the event mask, and are always reported).
>
> Note that the event mask should be checked at the point that the event
> (message) is queued (generated), not at the point it is dequeued (e.g.
> by XNextEvent).
>

OK.  This seems quite different than what the program was doing.  So to make
sure I understand, X applications always send a mask when then expect
something.  The server can decide what to do with any events that the
application hasn't asked for, by way of the mask, as long as they are events
which are in the mask.  If these aren't within the mask, then send them on
to the application.  If they are within the mask structure but not part of
the mask sent by the application, presumably they can be discarded.


Does that sound right?

Malcolm


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.281 / Virus Database: 149 - Release Date: 9/18/2001