• 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: Scattered NSProgress use
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Scattered NSProgress use


  • Subject: Re: Scattered NSProgress use
  • From: Jens Alfke <email@hidden>
  • Date: Fri, 17 Apr 2015 09:50:55 -0700

> On Apr 17, 2015, at 8:07 AM, Daryle Walker <email@hidden> wrote:
>
>> If you’d rather, you can make everything explicit by _never_ making an NSProgress current, and instead passing it in as the parent when you create new child instances.
>
> You can’t do that (for now). A progress object’s parent must be the current one or nothing (i.e. NIL); arbitrary parentage isn’t currently supported.

Oops, you’re right. What I’m actually doing is making the parent progress current, creating the child, then immediately resigning current. The point is not to separate making one progress current from creating a child.

—Jens
_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden


References: 
 >Scattered NSProgress use (From: Daryle Walker <email@hidden>)
 >Re: Scattered NSProgress use (From: Jens Alfke <email@hidden>)
 >Re: Scattered NSProgress use (From: Daryle Walker <email@hidden>)

  • Prev by Date: Re: User interface unresponsive in window
  • Next by Date: Re: Thousands of leaked CGContext ?
  • Previous by thread: Re: Scattered NSProgress use
  • Next by thread: Getting at NSTextFinder from text view
  • Index(es):
    • Date
    • Thread