On 15 mar 2009, at 01.14, Paul Sanders wrote:
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.
That's right. If you've established bindings to some property of an
object, it's no longer OK to update that property from background
threads.
Please refer to the Cocoa thread safety documentations:
<http://developer.apple.com/documentation/Cocoa/Conceptual/Multithreading/Introduction/Introduction.html
>
Not my area of expertise though, I have to say. Not in Cocoa
anyway. I am used to a more robust threading model.
I'm curious, what is not "robust" about the Cocoa threading model, and
what are you comparing it to?
j o a r
_______________________________________________
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
