eht@f.word.cs.cmu.edu (Eric Thayer) (02/03/90)
Anyone know the fix for appdefined events sitting in the event queue until some other event occurs? The documentation says that getNextEvent:waitFor:threshold: will wait for an event within the given timeout duration and with a priority equal to or greater than the given threshold. Ok, fine, I need to increase the priority for application defined events above what it is now. Because I get the event eventually (i.e. it is not a problem with the event mask), but it doesn't get processed until another event with a sufficiently high priority gets queued. Any clues? Also, the documentation concerning the Application run method is not correct. It says that run method calls getNextEvent:waitFor:threshold:. Try subclassing Application and overriding getNextEvent:waitFor:threshold:. It will not be called via the run method. -- Eric H. Thayer School of Computer Science, Carnegie Mellon (412) 268-7679 5000 Forbes Ave, Pittsburgh, PA 15213