• 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: Auto Threading of NSProgressIndicator
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Auto Threading of NSProgressIndicator


  • Subject: Re: Auto Threading of NSProgressIndicator
  • From: Nathan Day <email@hidden>
  • Date: Mon, 19 Aug 2002 22:17:28 +0930

What do you mean by doesn't exit, the resources for threads in Mac OS X are kept around so that they can be reused, create threads is time consuming.

On Monday, August 19, 2002, at 09:38 PM, email@hidden wrote:

I've done a little test with the AutoTheading feature that Quartz does when running a NSProgressIndicator.

When creating a NSProgressIndicator cirlce(wheel?) and sending the startAnimation:self it spawns a thread for itself. OK, this is great, it won't block the GUI, but wait after sending the stopAnimation:self to the same NSProgressIndicator it stops as it is supposed to do but the thead doesn't exit and waits until the application exits. Doesn't this waste resources?


Nathan Day
http://homepage.mac.com/nathan_day/
_______________________________________________
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: 
 >Auto Threading of NSProgressIndicator (From: email@hidden)

  • Prev by Date: Open, New, and Drag in DBA
  • Next by Date: Re:NSCountWindowsForContext : How to get the context ?
  • Previous by thread: Auto Threading of NSProgressIndicator
  • Next by thread: Open, New, and Drag in DBA
  • Index(es):
    • Date
    • Thread