In iOS 11, you don’t have to. Just let the observer go out of scope. There is no penalty any longer for letting an observer die before the observed or for letting the observed die before the observer, so you have no actual work to do. On the other hand, if you really want to … Read more
You still can implement -dealloc under ARC, which appears to be the appropriate place to remove the observation of key values. You just don’t call [super dealloc] from within this method any more. If you were overriding -release before, you were doing things the wrong way.
Short answer: No. Long answer: Nothing in UIKit is guaranteed to be KVO-compliant. If you happen to find that KVO-ing a property works, be grateful, it’s unintentional. Also: be wary. It could very well break in the future. If you find that this is something you need, please file an enhancement request. About your actual … Read more
Use a delegate if you want to talk to only one object. For example, a tableView has a delegate – only one object should be responsible for dealing with it. Use notifications if you want to tell everyone that something has happened. For example in low memory situations a notification is sent telling your app … Read more
There are usually notifications or other observable events where KVO isn’t supported. Even though the docs says ‘no’, it is ostensibly safe to observe the CALayer backing the UIView. Observing the CALayer works in practice because of its extensive use of KVO and proper accessors (instead of ivar manipulation). It’s not guaranteed to work going … Read more
But shouldn’t the synthesized accessors automatically return such a proxy object? No. What’s the proper way to work around this–should I write a custom accessor that just invokes [super mutableArrayValueForKey…]? No. Implement the array accessors. When you call these, KVO will post the appropriate notifications automatically. So all you have to do is: [myObject insertObject:newObject … Read more
Encapsulation If the ivar is private, the other parts of the program can’t get at it as easily. With a declared property, the clever people can access and mutate quite easily via the accessors. Performance Yes, this can make a difference in some cases. Some programs have constraints where they can not use any objc … Read more
You can use KVO in Swift, but only for dynamic properties of NSObject subclass. Consider that you wanted to observe the bar property of a Foo class. In Swift 4, specify bar as dynamic property in your NSObject subclass: class Foo: NSObject { @objc dynamic var bar = 0 } You can then register to … Read more
These are good questions, and its great to see that you’re doing this research and seem concerned with learning how to “do it right” instead of just hacking it together. First, I agree with the previous answers which focus on the importance of putting data in model objects when appropriate (per the MVC design pattern). … Read more