• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: CoreData relationships in IB
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CoreData relationships in IB


  • Subject: Re: CoreData relationships in IB
  • From: mmalcolm crawford <email@hidden>
  • Date: Sun, 22 May 2005 12:12:09 -0700


On May 22, 2005, at 11:44 AM, T Reaves wrote:

I have a UI setup to display and edit CoreData objects. I have ObjectA and ObjectB; ObjectA contains an ObjectB. On my UI I have fields for both ObjectA and ObjectB. The fields for ObjectB are bound to objectB.field. All well and good.

OK...

It does not appear that CoreData and the object controllers can instantiate the instance of ObjectB when objectB.field is set. Is this correct?

In what sense do you mean objectB.field is set?

Do I have to go ahead and create .h & .m files for my objects, and do the initialization of the contained objects there? Or is there a way to set this up in CoreData nd IB?

I'm not sure what is the relevance of the .h and .m files?

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


  • Follow-Ups:
    • Re: CoreData relationships in IB
      • From: T Reaves <email@hidden>
References: 
 >CoreData relationships in IB (From: T Reaves <email@hidden>)

  • Prev by Date: Re: Scroll bars in combo boxes
  • Next by Date: Re: CoreData relationships in IB
  • Previous by thread: CoreData relationships in IB
  • Next by thread: Re: CoreData relationships in IB
  • Index(es):
    • Date
    • Thread