Re: doesNotRecognizeSelector exception
Re: doesNotRecognizeSelector exception
- Subject: Re: doesNotRecognizeSelector exception
- From: Jeffrey Walton <email@hidden>
- Date: Sat, 26 Mar 2011 23:52:38 -0400
On Sat, Mar 26, 2011 at 11:48 PM, Quincey Morris
<email@hidden> wrote:
> On Mar 26, 2011, at 20:30, Jeffrey Walton wrote:
>
>> I'm not sure what its being sent to. below, I changed 'delegate' to
>> 'callbackDelegate' in case of a hidden name clash. Then I put in a few
>> NSLogs. The message is clearly not being sent to the delegate that was
>> init'd in the picker. The delegate changes from 0x1434b0 to 0x1283d0.
>
> This sort of thing can be caused by accidentally having 2 objects where you should only have one. For example, if you put a window controller object inside the window's nib file, that'll give you an extra window controller beyond the one that NSDocument (or the app delegate, depending on the kind of application) creates for you.
>
> They duel for a while, and then one of them possibly goes away because it's unreferenced.
>
> Why on earth aren't you using the debugger to track this down? Logging pointers is fine up to a point, but if you need to poke around to see if outlets are connected to what objects, it's a terribly inefficient way to debug.
>
Agreed. I don't have enough experience with Xcode and Cocoa yet to
know how to [correctly?] approach a problem. That, coupled with lack
of symbols, is crippling. It did not help that GDB's 'po' command
claimed the address was not even an object!
Jeff
_______________________________________________
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