Re: Spinning wait cursor in COCOA
Re: Spinning wait cursor in COCOA
- Subject: Re: Spinning wait cursor in COCOA
- From: Shawn Erickson <email@hidden>
- Date: Thu, 12 Feb 2004 17:29:37 -0800
I personally believe that no sensible situation exists that requires
you to busy the main thread instead of a secondary thread.
You may want the GUI to be modal while working on something but ways
exist to have that happen other then stalling event processing by
having your main thread chew on a long running task.
...regardless showing the beach ball is really never the right thing to
do on Mac OS X.
Note the Apple's HIG document, look at the suggestions at the bottom of
the following page.
<
http://developer.apple.com/documentation/UserExperience/Conceptual/
OSXHIGuidelines/index.html>
I bet NSCursor purposively doesn't provide access to the beach ball
cursor.
-Shawn
On Feb 12, 2004, at 4:54 PM, Matt Gillette wrote:
Although I do agree that normally you should use spinners within your
GUI, there are some circumstances where you don't want your process
running in other threads, so in such circumstances use
QDDisplayWaitCursor ( TRUE ) to bring the beach ball up quicker and
then pass it FALSE to stop the beach ball.
Matt
On Feb 12, 2004, at 8:34 AM, Shawn Erickson wrote:
Basically if your applications event queue isn't serviced by your
application (usually managed by NSApp using the main thread) after a
short amount of time (2 seconds?) the OS will put up the spinning
beach ball. In general one should attempt to avoid having it
displayed (use secondary threads for longer processes). Also it is
best to show a progress bar or spinner on you GUI in situations like
this then the beach ball... most folks using Mac OS X consider the
beach ball a sign of a hung/broken application.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.