On Fri, Jan 30, 2009 at 8:00 PM, Kyle Sluder <kyle.slu...@gmail.com> wrote: > On Fri, Jan 30, 2009 at 1:21 PM, A.M. <age...@themactionfaction.com> wrote: >> What is likely happening is that the NSFileHandle processing is starving the >> main NSRunLoop. This happens because NSRunLoop processes non-user input >> before it processes user events (which seems backwards for the main run loop >> but is nevertheless the case). > > Actually it makes perfect sense. If an event causes a method to call > -performSelector:withObject:afterDelay:, that selector should > logically be applied before the next event is processed.
That's an argument for prioritizing that one particular kind of event (assuming you meant with a 0 delay, anyway) but not an argument for prioritizing *all* non-user events. And even there, a continuous sequence of 0-delay performs should not lock the user out of your program. Seems to me that most non-user events should be interleaved in with user events based on when they occur, or at the very least given equal time. It's too easy to lock up the main event loop such that the user can no longer do anything otherwise. Mike _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
