Lists

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

Re: Key path help for complex binding

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

Re: Key path help for complex binding

Subject: Re: Key path help for complex binding
From: David Hirsch <email@hidden>
Date: Wed, 02 Dec 2009 11:47:23 -0800

This is quite helpful, Quincey, but one thing you wrote surprises me:

If you have a simple 'int' property backed by a single 'int' instance variable, changing the variable directly in your class implementation will not generate any KVO notifications. Changing the *property* -- which in that case means calling the setter method -- does generate KVO notifications. Of course, the setter implementation changes the backing variable.

Is that true, even if I write my own setter method (without willChange/ didChange)? If so, where is the notification coming from?

-Dave
_______________________________________________

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: Key path help for complex binding
From: Ken Thomases <email@hidden>


References:  
  >Key path help for complex binding (From: David Hirsch <email@hidden>)
  >Re: Key path help for complex binding (From: Quincey Morris <email@hidden>)
  >Re: Key path help for complex binding (From: David Hirsch <email@hidden>)
  >Re: Key path help for complex binding (From: Quincey Morris <email@hidden>)




Prev by Date:
Re: Application crashing on iPod Touch, not on iPhone

Next by Date:
Re: Contain touches within UIImageView only

Previous by thread:
Re: Key path help for complex binding

Next by thread:
Re: Key path help for complex binding

Index(es):

Date
Thread