🚀 go-pugleaf

In article <1992Aug31.143034.12176@visus.com> jml@visus.com (Jim Large) 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.
> 
>   I've found that some desirable things happen when -[Application run] is
> called.  The only one I know about for sure is that the application's icon
> (which is highlighted when you launch the app) becomes unhighlighted.

You have to be a bit careful even during the event loop itself.  [NXApp run]  
takes care of some things that are not events.  One example is reseting cursor  
rects (although you can easily set them explicitly to prevent this problem).   
There are other examples noted in the concept docs.

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?

--
--------------------------------------------------------------------
Paul Burchard	<burchard@math.utah.edu>
``I'm still learning how to count backwards from infinity...''
--------------------------------------------------------------------