Lists

Open Menu Close Menu

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

Re: Manual KVO and will/didChangeValueForKey

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

Re: Manual KVO and will/didChangeValueForKey

Subject: Re: Manual KVO and will/didChangeValueForKey
From: Tim Lucas <email@hidden>
Date: Fri, 3 Jun 2005 12:19:35 +1000

On 03/06/2005, at 10:42 AM, Andrew White wrote:

Why not just make a mirror? The key in question is a wrapper around a somewhat complex data structure. I'm not sure that the "willChangeValueForKey" semantics of recording the 'old' copy even make sense. A shallow mirror will only mirror the wrapper, not the detail. A deep mirror would be an unecessarily expensive operation.

How about exposing the object with an accessor and bind to it using the relevant keypath ("wrapper.property")?

- tim

_______________________________________________
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



References:  
  >Manual KVO and will/didChangeValueForKey (From: Andrew White <email@hidden>)
  >Re: Manual KVO and will/didChangeValueForKey (From: Tim Lucas <email@hidden>)
  >Re: Manual KVO and will/didChangeValueForKey (From: mmalcolm crawford <email@hidden>)
  >Re: Manual KVO and will/didChangeValueForKey (From: Andrew White <email@hidden>)




Prev by Date:
Re: combo box and objects?

Next by Date:
Re: NSLayoutManager looping with custom NSTextContainer

Previous by thread:
Re: Manual KVO and will/didChangeValueForKey

Next by thread:
Re: Manual KVO and will/didChangeValueForKey

Index(es):

Date
Thread