have it return no for this specific key, and then manually call
willChangeValueForKey:
and
didChangeValueForKey:
only when appropriate? It will end up being more lines of code, but it does seem like the more "correct" solution to the problem. Just a thought. Perhaps it isn't worth the extra code.
by Ross Boucher — Jan 19
Why not stop automatic support of KVO? Override
+ (BOOL)automaticallyNotifiesObserversForKey:(NSString *)aKey
have it return no for this specific key, and then manually call
willChangeValueForKey:
and
didChangeValueForKey:
only when appropriate? It will end up being more lines of code, but it does seem like the more "correct" solution to the problem. Just a thought. Perhaps it isn't worth the extra code.