> Rather than doing it every 1000 iterations, make it be time-based. Yes, I agree with you there. That's what I myself usually do in fact.
> I'm not sure what you're referring to when you talk about "other > techniques", but in general it is forbidden to access the GUI of a > Cocoa app from secondary threads, so you pretty much have to use > performSelectorOnMainThread: or some equivalent to update your GUI. I was referring to where the OP said: "but would it be safe, given the fact that sum and count are bound to some textFields/progressIndicator" And presumably it would not be as the instance variables referred to were being mutated in a secondary thread. Not my area of expertise though, I have to say. Not in Cocoa anyway. I am used to a more robust threading model. _______________________________________________ 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
