Re: Binding tablecolumn to attribute of specific object in to-many relationship?
Re: Binding tablecolumn to attribute of specific object in to-many relationship?
- Subject: Re: Binding tablecolumn to attribute of specific object in to-many relationship?
- From: Quincey Morris <email@hidden>
- Date: Tue, 29 Mar 2011 18:15:28 -0700
On Mar 29, 2011, at 14:57, Sean McBride wrote:
> I've considered adding a optional transient to-one relationship to
> Department named 'employeeId0' and binding the tablecolumn to
> departmentsArrayController>arrangedObjects>employeeId0>name, but maybe
> I'm barking up the wrong tree....
There's no obvious reason from your description why employee ID 0 needs to be a Core Data property. Surely it can just be a normal derived property.
Also, if it has no particular significance other than for populating the list, there's no real reason to implement the property in the data model itself. It seems more natural to implement it in your window controller.
But I don't see anything actually wrong with your original suggestion, if you have a compelling reason to go that way.
_______________________________________________
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