More or less. It appears that since the documentation in NSBundle does not state that its thread safe, it isn't.
>From Core Animation tho, it would appear that executing a CATransaction flush >may have resolved my original message, but perhaps not the problem. If I read this correctly, this updates the layers, which wouldn't otherwise be updated on a background thread. It would seem that if I call a non-thread safe function in a background thread, i.e., from an NSOperationQueue, that a compile or other error should result. On Sep 5, 2012, at 5:48 PM, Kyle Sluder <k...@ksluder.com> wrote: > On Sep 5, 2012, at 5:13 PM, John MacMullin <john.macmul...@cox.net> wrote: > >> Ok, that was it. I loaded [NSBundle loadNibNamed:XXX] in a background >> thread. >> >> Fixing that problem resolved the message. > > Did the process of fixing it also illuminate other areas you seem to be hazy > on, such as how Core Animation works, why loading nibs on background threads > is always incorrect, and how the debugger fits into the Xcode > edit/compile/debug cycle? > > --Kyle Sluder Best regards, John MacMullin _______________________________________________ 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
