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: Tue, 27 Dec 2005 23:55:44 +0000
On Sat Dec 24 11:22:47 2005, Michel Schinz wrote:
Without wanting to speak for Hamish, I think the problem is as
follows: if you want to have a method in an object which serves as a
proxy for a method in another object, you should be able to write
something as simple as:
- (SomeType*)proxyMethod:(SomeOtherType*)parameter {
return [otherObject originalMethod:parameter];
}
Thanks Michel, that's exactly right. 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.
What I would want is a mechanism similar to what one gets with
setKeys:triggerChangeNotificationsForDependentKey: but which would
work for properties of another object too.
I'd like this too, though perhaps in addition to being able to receive
willChange notifications for more complex dependency handling.
Thanks,
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