Re: KVO and the observeValueForKeyPath bottleneck
Re: KVO and the observeValueForKeyPath bottleneck
- Subject: Re: KVO and the observeValueForKeyPath bottleneck
- From: George Orthwein <email@hidden>
- Date: Fri, 21 Jul 2006 11:46:14 -0400
On Jul 21, 2006, at 4:11 AM, Scott Anguish wrote:
in my original reply, when I said controller I meant specifically
NS*Controller
So the only recommended application of "one way" bindings would be
between an NS*Controller and an NSView subclass, or also possibly
between an NS*Controller and a model class?
That's good to know and I don't think it's come up in past
discussions, or at least stated as plainly. The lack of any mention
of "one way" bindings is what I was referring to in the docs...
though it now seems that there is only a specific application for
them anyway. (Well, NS*Controller and a custom view should be pretty
common....)
It's a good point for this discussion though, since we seemed to be
settling in on:
True. I guess if you want to avoid the KVO "bottleneck" you can
just use "one way" bindings instead!
A general statement like doesn't work, since KVO can be used in
situations where "one way" bindings aren't recommended (Matt's
position notwithstanding :) ).
Thanks,
George
_______________________________________________
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