Re: Core Data/IB questions
Re: Core Data/IB questions
- Subject: Re: Core Data/IB questions
- From: "Adam Gerson" <email@hidden>
- Date: Thu, 27 Mar 2008 02:34:38 -0400
I think that internally when you create a to-many core-data
relationship the group of objects is stored as an NSSet as opposed to
an array.
http://developer.apple.com/documentation/Cocoa/Reference/Foundation/Classes/NSSet_Class/Reference/Reference.html
http://developer.apple.com/documentation/Cocoa/Conceptual/CocoaBindings/Concepts/CntrlContent.html#//apple_ref/doc/uid/TP40002147-181724
http://developer.apple.com/documentation/Cocoa/Conceptual/KeyValueCoding/Concepts/AccessorConventions.html#//apple_ref/doc/uid/20002174-178830-BAJEDEFB
On Thu, Mar 27, 2008 at 2:10 AM, Rick Mann <email@hidden> wrote:
>
> On Mar 26, 2008, at 11:06 PM, Adam Gerson wrote:
> > Each table should have its own ArrayController if the two tables
> > represent the data from two different entities. Since you entities are
> > related I am assuming one entity has a property that is a to-many
> > relationship to the other entity. Set the ContentSet bindings for
> > ArrayController2 to be the selection of ArrayController1.
> >
> > ArrayController2 ContentSet
> > Bind to = ArrayController1
> > Controller Key = selection
> > Model Key Path = (the name of the relationship that represents entity2
> > in entity1)
> >
> > This will cause ArrayController2 to always populate the TableView with
> > the objects selected by ArrayController1
> >
> > Let me know if that needs to be more clear.
>
>
> Excellent! That was exactly what was missing. Thank you.
>
> Why ContentSet, and not ContentArray or one of the other ContentXXX
> things?
>
> --
> Rick
>
>
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden