An instance 0x30fda0 of class <My Window Controller Class> is being
deallocated while key value observers are still registered with it.
Break on _NSKVODeallocateLog to start debugging.
I'm assuming this message indicates a problem with the implementation
for my window controller class, and I would like to eliminate that
problem. What is needed to prevent this message from occurring?
removeObserver:forKeyPath: is the equivalent for
addObserver:forKeyPath:options:context, which is call by the object that
wants to observe the value.
Since the observing object registers itself, it seems that the same
object should de-register itself as well. I'm not sure how every
registered object is supposed to know that the window controller is
deallocating itself so they can de-register themselves.
If the window controller should de-register the observers instead. I'm
not sure how it is supposed to know about all its observers. I can't
find a method that will provide that kind of information. It seems that
the window controller would have to override
addObserver:forKeyPath:options:context so it can perform the task of
tracking the registered observers, even though the super class is doing
that already.
How is all this de-registration supposed to work?
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
