🚀 go-pugleaf

In article <1992Sep1.002728.15172@fcom.cc.utah.edu> burchard@horizon.math.utah.edu (Paul Burchard) writes:
>> In article <1992Aug25.092051@fdr.jsc.nasa.gov> shirley@fdr.jsc.nasa.gov (Bill  
>> Shirley [CSC]) writes:
>> > 
>> > Does the -run method of Application NEED to be invoked.
>> > I need a little bit more control over the event loop.
>
>There really should be a way to "flush" NXApp, dispatching all pending events  
>and performing any other NXApp chores, and then returning.  I do not know of  
>any way to kludge this with the current API (the modal loop methods almost fit  
>the bill but they all discard some events).
>
>I would suggest NeXT add the following method to NXApp to achieve this:
>
>	- flushEvents:(int)mask waitFor:(double)timeout threshold:(int)level
>
>with parameters analogous to -getNextEvent:waitFor:threshold:.  Anyone at NeXT  
>listening?

Can't you do this by putting a stop message in the queue and then calling
[NXApp run]? The run will return if a 'stop' is seen, but can you call
run from within run (I.e., is it re-entrant), or do you have to re-write the
main() routine?

I agree that 'flushEvents' would be a cleaner way, but cleaner yet would
be '[NXApp flushEvents]'.

		Michael
-- 
		Michael Gersten		michael@stb.info.com
HELLO! I'm a signature virus! Join in the fun and copy me into yours!
ex:.-1,. w $HOME/.signature