Path: utzoo!mnetor!uunet!husc6!think!ames!pasteur!ucbvax!decwrl!hplabs!hpda!hp-sde!hpfcdc!hpfcdq!elliott
From: elliott@hpfcdq.HP.COM (Ian Elliott)
Newsgroups: comp.windows.x
Subject: Re: missing event reading functionality
Message-ID: <890002@hpfcdq.HP.COM>
Date: 4 May 88 15:53:15 GMT
References: <294@piring.cwi.nl>
Organization: Hewlett-Packard - Fort Collins, CO
Lines: 29

/ guido@cwi.nl (Guido van Rossum) /  3:43 pm  May  2, 1988 /

> Looking through chapter 8 of the Xlib documentation I find that the
> event reading/checking routines can be organized in a matrix, as
> follows:
> 
> 		| get event,	| get event,		| read event but
> 		| block if 	| return False		| leave it in queue
> 		| necessary	| if none queued	| (may block)
> ----------------+---------------+-----------------------+------------
> plain		| XNextEvent	| ?			| XPeekEvent
> w/ predicate	| XIfEvent	| XCheckIfEvent		| XPeekIfEvent
> for a window	| XWindowEvent	| XCheckWindowEvent	| ?
> w/ event mask	| XMaskEvent	| XCheckMaskEvent	| ?
> w/ type		| XTypeEvent	| XCheckTypeEvent	| ?
> 
> The hole on the top row is almost, but not completely, filled by
> XPending; but it doesn't read the event if there is one (and its name
> isn't XCheckEvent :-).

I would also like to put a plug in for the addition of an XCheckEvent (or
XCheckNextEvent) procedure!  I have some code that really needs that
functionality.

						Ian Elliott

ARPA:	elliott%hpfcian@hplabs.HP.COM
UUCP:	hplabs!hpfcla!elliott
Tele:	(303) 229-4272