Path: utzoo!attcan!uunet!husc6!mailrus!ames!pasteur!ucbvax!decwrl!hplabs!hpda!hp-sde!hpfcdc!hpfclp!diamant
From: diamant@hpfclp.SDE.HP.COM (John Diamant)
Newsgroups: comp.windows.x
Subject: Re: X docs needed
Message-ID: <9740025@hpfclp.SDE.HP.COM>
Date: 24 May 88 15:51:12 GMT
References: <5600@chinet.UUCP>
Organization: HP SDE, Fort Collins, CO
Lines: 27

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

Thanks.  That sounds great.

> 	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.

Could you clarify what work procs are?  I can't find any such reference
in the documentation or code.  The only handling I find in XtNextEvent
is for destroylists and input and timer procedures.  The only thing
I can think that you might mean is a generic term for callbacks, event
handlers, etc.

> 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.

That's very good to hear.  Both interface approaches are useful and a
mix is probably the best combination.  Thanks,

John Diamant
Software Development Environments
Hewlett-Packard Co.		ARPA Internet: diamant@hpfclp.sde.hp.com
Fort Collins, CO		UUCP:  {hplabs,hpfcla}!hpfclp!diamant