On Mon, Mar 31, 2008 at 2:26 PM, Jeff LaMarche <[EMAIL PROTECTED]> wrote:
> 4) You can, as Ben mentioned, use performSelector:onMainThread: to > actually have the object inserted on the main thread's context. It's a bit > of a pain, but threads are always at least a little painful. > How? Core data says that to use NSManagedObjects between threads you need to pass an ID and access it from another context. But you don't even get an ID until you perform a save on the original context. I'm then back to my original problem where the save itself takes too long. >From what I've read so far, my current thinking is that I need to give up on Core data. I can easily create my own objects, handle my own locking or synchronization. I was thinking to still use NSTreeController bound to my objects. Its a shame because core data sounds so cool. I love the data modeling aspects. Nice way to think through the problem even if I end up not using it. _______________________________________________ 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 [EMAIL PROTECTED]
