Re: Scattered NSProgress use
Re: Scattered NSProgress use
- Subject: Re: Scattered NSProgress use
- From: Daryle Walker <email@hidden>
- Date: Fri, 17 Apr 2015 11:07:16 -0400
On Apr 13, 2015, at 12:33 PM, Jens Alfke <email@hidden> wrote:
>
>> On Apr 11, 2015, at 12:49 PM, Daryle Walker <email@hidden <mailto:email@hidden>> wrote:
>>
>> We have to make sure that the automatic parent/nesting aspect doesn’t make sibling & cousin progress objects, whose actions will be interlaced, interfere with each other.
>
> It’s only automatic while an NSProgress is made the currentProgress, and currentProgress is a per-thread state. So you’re in control of what code runs, and what other NSProgresses are created, while one is current. 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.
—
Daryle Walker
Mac, Internet, and Video Game Junkie
darylew AT mac DOT com
_______________________________________________
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