Re: KVO one-step listening but two-step notifying?
Re: KVO one-step listening but two-step notifying?
- Subject: Re: KVO one-step listening but two-step notifying?
- From: Hamish Allan <email@hidden>
- Date: Mon, 2 Jan 2006 13:47:04 +0000
On Tue, 27 Dec 2005 16:00:16 -0800, mmalcolm crawford wrote:
On Dec 27, 2005, at 3:55 PM, Hamish Allan wrote:
And I think the related question implied by the subject line --
why must I provide notifications before and after the change, when
I can only receive them after the change? -- still stands.
Again, that's just the way it works. In the notification you can
(in theory at least...) get the old and new values, so if you need
to calculate a delta between old and new you can do so.
I don't care about the delta. Unfortunately, some other part of the
framework does... but by the time I am given the opportunity to
present the delta to that part of the framework, it is already too
late for the framework's purposes.
It seems clear to me and at least a couple of others that there is an
problem with this, but not to you. I'd like to file a bug report, but
I'm obviously not doing a very good job of explaining the problem.
Is it just not plain to you why someone might want to proxy data
without making a copy of it? Daniel's locally-cached remote model
seems to me to be a good example of this.
Best wishes,
Hamish
_______________________________________________
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