Re: suppressing the scod at startup
Re: suppressing the scod at startup
- Subject: Re: suppressing the scod at startup
- From: Joshua Scott Emmons <email@hidden>
- Date: Mon, 23 Jan 2006 17:08:13 -0600
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.
Huh, that is funny. I've never thought of the pinwheel as being a
harbinger of crashes. It seems like every GUI I've used has an
hourglass or wristwatch, or some sort of "don't click" pointer to
indicate when a program's interface won't accept input from the
mouse. I've always thought OS X's (and NeXTStep's, for that matter)
was the spinning wheel. It's true that OS X correctly sets this
pointer for applications that have crashed (seeing as a crashed
program cannot except clicks). But it seems wrong to then correlate
the "no click" pointer with crashes. Why not correlate it with "you
can't click on this"? I suppose it depends which you see more of:
busy applications or crashed applications, eh?
Regardless, it's still true that all of my non-Adobe, splash-screen-
sporting programs display a spinning wheel while loading. From
Microsoft Office to Final Draft. I would be hesitant to override what
would appear to be accepted behavior unless I had a large folder of
usability studies to back me up.
Cheers,
-Joshua Emmons
_______________________________________________
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