• 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: indeterminate progress bar animation problem
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: indeterminate progress bar animation problem


  • Subject: Re: indeterminate progress bar animation problem
  • From: Hamish Allan <email@hidden>
  • Date: Mon, 18 Apr 2005 10:44:37 +0100

On Sun, 17 Apr 2005 20:43:39 -0400, Ivan Kourtev <email@hidden> wrote:

I was only able to get the barber pole to show progress if I kept the
setUsesThreadedAnimation  line above.  If I changed the barber pole to
the spinning indicator, then it worked without requiring
setUsesThreadedAnimation.

Hmm, strange. This suggests to me that the spinning indicator automatically sets the use of threaded animation. Anyone else know about this?


What's going on or is this expected behavior (not what I would think
based on NSProgressIndicator's documentation)?  Apple's documentation
suggests that using setUsesThreadedAnimation:YES may slow down the app
so I figured there has to be a way to animate the barber pole while
setUsesThreadedAnimation:NO.

I think this is the expected behaviour: either you use threaded animation, or the animation advances one frame in each run loop.


Multithreaded apps have more overhead than single-threaded ones, but done properly they tend to give the user the impression of running faster anyway. With dual core processors on the immediate horizon, I don't see myself ever again writing anything single-threaded other than the simplest of programs.

I also avoid indeterminate progress indicators unless I really can't reflect true progress in a determinate one. If you write the data in a separate thread, updating a determinate progress indicator as you go (i.e., write it out in chunks) your users will be better informed (and using multithreading means they won't get the spinning beach ball of death, either).

Also, does this code above appear to be the correct to implement the
required behavior (save panel sheet, followed immediately by a "Please
wait while saving..." sheet with the spinning barber pole).

Looks fine to me.

Best wishes,
Hamish

_______________________________________________
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


  • Prev by Date: Re: Error inserting object at arranged index
  • Next by Date: dragging from a view to editors and the finder
  • Previous by thread: indeterminate progress bar animation problem
  • Next by thread: NSBezierPath Glypths
  • Index(es):
    • Date
    • Thread