Re: NSTreeController and Core Data.
Re: NSTreeController and Core Data.
- Subject: Re: NSTreeController and Core Data.
- From: Óscar Morales Vivó <email@hidden>
- Date: Mon, 4 Jul 2005 16:33:19 -0400
That makes things a lot more clear, although I'm not sure why
addChild isn't working properly in my case since from what I read it
does the right thing. I believe it does have to do with the fact that
the 'parent' relationship (the reverse of the children one) is to-
many. Maybe Core Data is expecting a to-one reverse relationship when
creating the object and doesn't know what to do.
As an aside, I'd think object creation would be a nice thing to deal
with using a delegate, instead of having to subclass the controller
class for it. I'll file enhancement requests both for the
documentation shortcomings and for that.
Thanks a lot:
Oscar Morales Vivo.
On Jul 4, 2005, at 02:47 , mmalcolm crawford wrote:
On Jul 3, 2005, at 9:42 PM, Óscar Morales Vivó wrote:
However I'm not sure whether I can somehow use the controller's
addChild/InsertChild (now, what was the difference between them?)
methods to populate the database, or whether I need to subclass
the NSTreeController to override those methods and configure the
new objects properly. There doesn't seem to be any way to tell the
controller to set the relationships when creating new child
objects, but I've seen the frameworks do similar insights before.
Does this thread help?
<http://www.cocoabuilder.com/archive/message/cocoa/
2005/6/22/139753>
mmalc
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden