|[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]|
I'm just curious about how people are handling the fact that when you do KVO, all your notifications are bottlenecked through a single method, observeValueForKeyPath:... This is a very unpleasant and crude architecture (in contrast to NSNotification where, when a notification comes in, it is automatically routed to the selector of your choice). I really don't want a series of "ifs" here. I can imagine a simple dispatcher architecture based on NSSelectorFromString; is this the sort of thing people are using? Thx - m. -- matt neuburg, phd = email@hidden, <http://www.tidbits.com/matt/> A fool + a tool + an autorelease pool = cool! AppleScript: the Definitive Guide - Second Edition! <http://www.amazon.com/gp/product/0596102119> _______________________________________________ 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
Visit the Apple Store online or at retail locations.
Copyright © 2011 Apple Inc. All rights reserved.