Re: suppressing the scod at startup
Re: suppressing the scod at startup
- Subject: Re: suppressing the scod at startup
- From: Matt Neuburg <email@hidden>
- Date: Mon, 23 Jan 2006 19:50:53 -0800
- Thread-topic: suppressing the scod at startup
On Mon, 23 Jan 2006 15:48:08 -0800, Shawn Erickson <email@hidden> said:
>On 1/23/06, Daniel Jalkut <email@hidden> wrote:
>> It's funny to hear this perspective, because I still consider the
>> spinning wheel to be the "program might have crashed" of the new
>> millennium.
>>
>> I also find the wristwatch a little funny - best of all is when the
>> program is in enough control of its execution that it can present
>> standard UI in a window that conveys a sense of business alongside
>> progress.
>
>Apple's take on this...
>
>"For potentially lengthy operations, use a progress indicator to
>provide useful information about how long the operation will take.
>Users don't need to know precisely how many seconds an operation will
>take, but an estimate is helpful. For example, Mac OS X uses
>statements such as "about a minute remains" to indicate an approximate
>time frame. It can also be helpful to communicate the total number of
>steps needed to complete a taskĀfor example, you might include text
>that says "Copying 30 of 850 files."
>
>Note: A good reason to provide feedback during lengthy operations is
>that if your application fails to respond to events for 2 seconds, the
>system automatically displays a busy cursor for your application.
>Users who see this cursor without any other feedback might think that
>your application is frozen and quit it using the Force Quit window."
>
>- From
<http://developer.apple.com/documentation/UserExperience/Conceptual/OSXHIGuideli
nes/XHIGHIDesign/chapter_5_section_2.html#//apple_ref/doc/uid/TP30000353-TPXREF1
06>
>
>It is likely much better to display a dialog with a determinate
>progress indicator (if possible) or even the real application window
>with asynchronous progress indicator to let the user know that
>something is taking place.
>
><http://developer.apple.com/documentation/UserExperience/Conceptual/OSXHIGuidel
ines/XHIGControls/chapter_18_section_5.html#//apple_ref/doc/uid/TP30000359-TPXRE
F106>
As I said, I'm doing all that. I've put up a splash screen, and it has some
animation which gives the impression that the app is doing something. Now,
as a final touch, I'd like also to make the scod go away. But I don't know
how. The problem is apparently that when an XML-based Core Data app starts
up, the data is loaded (the mere unarchiving from the nib of an
NSArrayController bound to the managed object controller is evidently
sufficient to cause this), and since I don't get any feedback while this is
going on, and since it happens on the main thread, I don't see how to stop
the scod. (I cannot post any events to the main thread, because Core Data is
blocking it while it loads the data.) But surely others have grappled with
this problem, right? m.
--
matt neuburg, phd = email@hidden, <http://www.tidbits.com/matt/>
A fool + a tool + an autorelease pool = cool!
AppleScript: the Definitive Guide
<http://www.amazon.com/exec/obidos/ASIN/0596005571/somethingsbymatt>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden