Re: doesNotRecognizeSelector exception
Re: doesNotRecognizeSelector exception
- Subject: Re: doesNotRecognizeSelector exception
- From: Jeffrey Walton <email@hidden>
- Date: Sat, 26 Mar 2011 23:28:16 -0400
On Sat, Mar 26, 2011 at 11:26 PM, Kyle Sluder <email@hidden> wrote:
> I'm on the road so i cant discuss this further right now. One reason it's more helpful to keep this discussion on-list. :)
>
> --Kyle Sluder
My Bad. I sometimes forget that GMail does not perform a 'Reply All' by default.
Jeff
>
> On Mar 26, 2011, at 8:23 PM, Jeffrey Walton <email@hidden> wrote:
>
>> On Sat, Mar 26, 2011 at 11:01 PM, Jeffrey Walton <email@hidden> wrote:
>>> On Sat, Mar 26, 2011 at 10:37 PM, Kyle Sluder <email@hidden> wrote:
>>>> On Sat, Mar 26, 2011 at 7:35 PM, Sherm Pendley <email@hidden> wrote:
>>>>> The delegate message is being sent to an instance of UIView - not to
>>>>> your controller. That would indicate that the first argument you're
>>>>> sending to -initWithDelegate:withContext: is not what it should be.
>>>>
>>>> Or nobody's retaining the delegate, and therefore it's being replaced
>>>> in memory with the UIView instance. The reason delegates are
>>>> unretained in Cocoa is because they typically have a strong reference
>>>> to the thing they are a delegate of.
>>> Correct: the file picker is not retaining the delegate (per Hillegass
>>> and retain loop/cycle).
>>>
>>> Should the delegate be retained by FilePicker? In this case, to avoid
>>> the retain loop, MyViewController *should not* retain the FilePicker?
>> Changing the code so that the FilePicker retained the delegate did not help.
>>
>> 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