• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: cursor ills
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: cursor ills


  • Subject: Re: cursor ills
  • From: "M. Uli Kusterer" <email@hidden>
  • Date: Thu, 2 Oct 2003 22:40:58 +0200

At 15:21 Uhr -0400 02.10.2003, robert l clair wrote:
In my limited sample, 5 or so, they don't think of
it as the wait cursor - they think of it as the "spinning ball of death" cursor. If it disappears
and the app comes back it isn't like "Oh it finished doing what it was doing" it's more "A near
death experience miraculously averted." I think the problem is that (1) it doesn't appear immediately
when a potentially lengthly operation starts and (2) at least on a perceptual basis the delay before
it starts doesn't feel consistent. It think that a application controlled wait cursor, used consistently,
would make them happier.

It *is* the spinning beach ball of death. Wherever did you get the idea that it was a "wait" cursor? Hogging the CPU for a lengthy amount of time without responding to events is considered bad form for an application on a modern, pre-emptively threaded, multi-tasked OS.

Look at the Finder: Normally, it displays the "spinning watch cursor" when it's doing something lengthy, and it also handles events at least in a limited fashion (you could run a nested run loop, for example, which takes care of handling window redraws, though even better would be just to fire a separate NSThread to actually take care of the busywork, and let the user keep on working with your app as she pleases).

It's a feature, not a bug. It's Apple's way of telling you to rethink your application's design, instead of messing about as you would have done on those old single-tasked OSs.

In the good old MultiFinder days, Apple tried by asking nicely with their cooperative multitasking. That didn't work, so now they just force you to do the right thing by otherwise forcing the beach ball upon you.

(OK, there is an API to turn off the beach ball, but if you really think you have to do a bad design, find it yourself... :-p )
--
Cheers,
M. Uli Kusterer
------------------------------------------------------------
"The Witnesses of TeachText are everywhere..."
http://www.zathras.de
_______________________________________________
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.
References: 
 >cursor ills (From: robert l clair <email@hidden>)

  • Prev by Date: Re: MainMenu and NSDocument problems
  • Next by Date: scroll view & pinned edge during resize
  • Previous by thread: cursor ills
  • Next by thread: Re: cursor ills
  • Index(es):
    • Date
    • Thread