On Oct 7, 2016, at 02:28 , J.E. Schotsman <jesc...@xs4all.nl> wrote: > > It isn’t mentioned in the NSProgress Overview though.
You are correct about that, which makes me wonder how much of my understanding I simply dreamed. Looking at the documentation a bit more carefully, though, I think it’s implicit. Each thread, it says, can have a “current” NSProgress object, but there can be parent-child relationships between NSProgress objects across thread boundaries. Thus, it’s perhaps not that any individual NSProgress object trampolines properties across thread boundaries, but that the parent-child communication is thread-safe. IIRC, the way the code is structured, where I’ve used NSProgress, is that there’s a root NSProgress associated with the NSWindowController/NSViewController that’s driving the progress dialog, and there’s one or more child NSProgress objects associated with each background thread that does partial work for the overall operation. I’m not sure I’ve ever tried multi-thread access to any *single* NSProgress object’s properties. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
