Re: Who is responsible for removing observers in longer key paths [solved]
Re: Who is responsible for removing observers in longer key paths [solved]
- Subject: Re: Who is responsible for removing observers in longer key paths [solved]
- From: Per Bull Holmen <email@hidden>
- Date: Fri, 02 Mar 2012 01:11:06 +0100
Den 22:58 1. mars 2012 skrev Quincey Morris
<email@hidden> følgende:
> You can *try* dealloc voodoo, but I think it's crucial to look at the
> observerInfo in the debugger. And, the number of remaining observers may be
> more informative than what they are.
Hi
Sorry it took a little while to get back to you. It turns out, once I
changed the superclass of my controller to NSObject instead of
NSController, the problem was solved. You couldn't possibly have
figured that out. NSController inherits from NSObject, but clearly
some of the behaviour regarding registering and managing key-value
observers is overridden. The only thing Apple docs says about the
class is that it implements the <NSEditorRegistration> protocol, which
I thought might be a benfit, but clearly it does something more too.
Something which belongs to the Mysteriously Unknown and that I
probably don't need.
Thanks.... :)
Per
_______________________________________________
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
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden