At 0:21 -0500 31/1/09, Michael Ash wrote:
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
On Jan 30, 2009, at 2:08 AM, Rick Mann wrote:
Sorry for the cross-post, but I thought both these lists might have
advice to offer.
Please don't cross-post. Try one list, then the other.
I just dusted off an app I'd worked on several months ago. It used
to work fine (prior to 10.5.6), but
On Jan 30, 2009, at 10:21:35, A.M. 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
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
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
