Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Better to chain key path dependencies, or list explicitly?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Better to chain key path dependencies, or list explicitly?

Subject: Better to chain key path dependencies, or list explicitly?
From: Rick Mann <email@hidden>
Date: Tue, 19 May 2009 16:24:49 -0700

I have some key paths dependent on other paths. I'm using +keypathsForValuesAffectingFoo to set up the dependency.

Now I have a chain of dependencies: A -> B -> C. Is it better to just have B depend on C, and A depend on B, or should A explicitly depend on B and C?

TIA,
--
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


Follow-Ups:

Re: Better to chain key path dependencies, or list explicitly?
From: Ken Thomases <email@hidden>


Prev by Date:
Re: Bindings and KVO of View objects

Next by Date:
Re: Programatically set file URL of Core Data Document?

Previous by thread:
Re: Bindings and KVO of View objects

Next by thread:
Re: Better to chain key path dependencies, or list explicitly?

Index(es):

Date
Thread