• 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: Binding to values which aren't there
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Binding to values which aren't there


  • Subject: Re: Binding to values which aren't there
  • From: BareFeet <email@hidden>
  • Date: Mon, 12 Oct 2009 10:25:56 +1100

On 10/10/2009, at 9:17 AM, A B wrote:

Long-held habits regarding best practices regarding relational integrity are making me reluctant to stick a "parentPerson" ivar in each Note object, otherwise the solution would be simple: Just create another property which has code in the getter that calls back to the parent object (the structure of which would then have to be known to the Note object) for the birthday, does the necessary math and then returns the result.

Why not create the parentPerson ivar the Note object? Since you want the Note to access a property of the parent Person, this seems logical to me and, as you said, makes the solution simple.


Tom
BareFeet

_______________________________________________

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


References: 
 >Binding to values which aren't there (From: A B <email@hidden>)

  • Prev by Date: Re: A question involving properties
  • Next by Date: Writing NSArray data to file, and compression
  • Previous by thread: Re: Binding to values which aren't there
  • Next by thread: using QLPreviewPanel and supporting 10.5
  • Index(es):
    • Date
    • Thread