Re: Preventing beach balls
Re: Preventing beach balls
- Subject: Re: Preventing beach balls
- From: Michael Watson <email@hidden>
- Date: Mon, 19 Feb 2007 17:27:29 -0500
On 19 Feb, 2007, at 17:22, Stefan Werner wrote:
On Feb 19, 2007, at 10:40 PM, Uli Kusterer wrote:
Am 19.02.2007 um 04:52 schrieb Dave Sopchak:
I can't help but think this whole thread would be unnecessary if
Apple had simply decided to use an updated watch cursor in OS X,
rather than the spinning beach ball. Ugh.
Whenever your app doesn't process events for a while, you get the
beach ball. That's either a sign your app has hung, or it's not
been engineered the way Apple wants you. Had they used the watch
cursor, you would see that cursor whenever an app hangs. There's
not much difference in what image they use.
There's one slight difference:
"You can tell the busy cursor not to stay animated if your
application stops responding. This ensures that the busy cursor
won't spin forever if your application never returns from a task."
source: http://developer.apple.com/documentation/mac/
MacAppProgGuide/MacAppProgGuide-114.html#HEADING114-76
Stefan
That doesn't stop the app from being unresponsive, which has nothing
to do with the animation or image of the cursor. That's what we're
talking about: there is no functional difference between the old-
style wait cursor and the new-style wait cursor.
--
m-s
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden