On 26 maj 2009, at 08.03, Mike Abdullah wrote:
Wow, I had no idea of this particular aspect of the rules. My suspicion is this exists to accomodate Cocoa's ability to use window objects for caching a view's contents to an image. Maybe the act of showing a window is what is breaking on a secondary thread.
Perhaps so. While the guidelines states that it's safe to create the window, that still leaves basically everything else in the NSWindow API off bounds for use from background threads - including calling "- orderFront:" to show the window.
The general recommendation has to be to only manipulate the UI from the main thread. With a few exceptions, the thread safety guidelines are currently not detailed enough to allow for anything else.
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
