Re: KVO and the observeValueForKeyPath bottleneck
Re: KVO and the observeValueForKeyPath bottleneck
- Subject: Re: KVO and the observeValueForKeyPath bottleneck
- From: Chris Kane <email@hidden>
- Date: Mon, 17 Jul 2006 09:09:04 -0700
On Jul 17, 2006, at 7:38 AM, Matt Neuburg wrote:
On or about 7/17/06 3:38 AM, thus spake "Jakob Olesen"
<email@hidden>:
- (void)observeValueForKeyPath:(NSString *)keyPath ofObject:(id)
object change:(NSDictionary *)change context:(void *)context
{
if ([self respondsToSelector:(SEL)context])
[self performSelector:(SEL)context withObject:change];
}
By an incredible coincidence, yesterday (before this reponse
arrived at my
desk), after considering all the responses I'd gotten, I decided
upon an
approach and implemented it in my app, and it was word for word,
letter for
letter identical with this. m.
I'm just curious ... with the trivial approach above, and the other
ones involving the context being a keypath and so on ... has anyone
considered what will happen if a superclass or subclass (of whatever
class that is) is also doing KVO (on either same or different keys)
of the same objects?
Chris Kane
Cocoa Frameworks, Apple
_______________________________________________
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