Yeah, I just kind of avoided the basic problem. The app isn't
receiving at least some events -- for example the menus can't be
pulled down. On the other hand, the spinning beach ball doesn't
appear, and I can drag the progress window around.
I'll have to see if a cancel button will work.
Of course putting the code in another thread would be a big change.
Jim Merkel
On Jun 20, 2011, at 1:14 AM, Kyle Sluder wrote:
On Jun 20, 2011, at 12:36 AM, James Merkel <jmerk...@mac.com> wrote:
It turns out if I use setUsesThreadedAnimation:YES on the progress
indicator, the bar indicator animates.
The docs say this method sets a hint as to whether the receiver
should implement animation of the progress indicator in a separate
thread. I guess the hint is taken and the animation is performed
in a separate thread.
You still haven't addressed the question of whether you're blocking
the main thread.
According to your pseudocode, you are. This is very bad. The
spinning beach ball cursor will appear while your app is performing
its "long processing," and there will be no way for your app to
receive any events from the user asking it to cancel.
I look forward to the day when OS X automatically kills beachballing
programs after a certain time, a la iOS. Because then maybe iTunes
will finally get rewritten.
--Kyle Sluder
_______________________________________________
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
