Re: Lots of Core Data Attributes
Re: Lots of Core Data Attributes
- Subject: Re: Lots of Core Data Attributes
- From: Todd Yandell <email@hidden>
- Date: Fri, 1 Jul 2005 02:31:20 -0500
On Jun 30, 2005, at 10:27 PM, mmalcolm crawford wrote:
You could instead define an Address entity and individual
relationships for each address:
I'm convinced now that it's worth it do this with relationships.
There's still a problem with this approach for me, though. That is
that I'd like to do it all with an NSArrayController, with
NSObjectController's representing the address relationships. This
would work well if the address objects already existed when the user
creates a new "person" object, but since they do not, all the user
sees in the various address fields is "No Selection". At least, I
assume that's what the problem is. I admit, I don't have a great
amount of experience with bindings, but as far as I can tell, this is
what's causing the problem. (Also, because I wasn't very clear in my
original email, this is why I was wondering if I should just use
attributes instead).
I think the best way to describe what's going on would be with an
example project. If you have the time, I'd really appreciate it if
you could take a look at the project at the link below and offer any
advice you might have on fixing the "No Selection" problem.
http://hub.peppermedia.net/cocoa/Contacts.zip
Thanks for your help!
Todd Yandell
_______________________________________________
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