Path: utzoo!attcan!uunet!husc6!bloom-beacon!WSL.DEC.COM!haynes
From: haynes@WSL.DEC.COM
Newsgroups: comp.windows.x
Subject: Re: X docs needed
Message-ID: <8805210007.AA01036@gilroy.dec.com>
Date: 21 May 88 00:07:27 GMT
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 26

Calling XtNextEvent and XtDispatch event yourself inside XtMainLoop
will work. There are a few things to be careful of:

	If you don't consume the event, you better push it back and return
	or be prepared to deal with the consequences of ignoring events.

	In older versions of the intrinsics, deleting widgets actually happened
	at the next XtNext event. This is wrong in the case of recursive
	event dispatching, and has been fixed in the latest spec. If you aren't
	deleting widgets in any of this code, don't sweat this.

	Work procs are handled by XtNextEvent. If you register work procs
	at various levels of the recursion, they should be willing to be invoked
	at different levels than they were registered.


The toolkit was explicitly designed to make it possible have either a
"pull" (read/blocking) model of the world or a "push" (event
driven/non-blocking) model of the world. We also believe that it is
possible to mix the two views.

The bottom line is that it will work, but you have to exercise some
care. These are power tools you're dealing with...

	Have at it!
	-- Charles