Re: -[NSProxy doesNotRecognizeSelector: error
Re: -[NSProxy doesNotRecognizeSelector: error
- Subject: Re: -[NSProxy doesNotRecognizeSelector: error
- From: Shane Stanley <email@hidden>
- Date: Thu, 22 Aug 2013 17:43:52 +1000
On 22/08/2013, at 3:42 PM, Graham Cox <email@hidden> wrote:
> Is there is any possibility that 'self' is not what you think it is? If that's confused, then the proxy is simply reflecting the fact that the object 'self' points to doesn't respond to the selector (since its own -respondsToSelector: method just calls the target's).
Not that I can see. Unless...
>
>> It's called in a block using:
>>
>> [[NSOperationQueue mainQueue] addOperationWithBlock:^{
>
> Is there a good reason to do this? Adding an operation to the main queue doesn't really give you much. Blocks complicate things. If you can just call your undo manager -prepare… directly at the point where it's needed, it might flush out the problem, or even fix it.
The process takes a fair amount of time -- it could even be a minute or more -- so I'm doing it on a background operation queue. Only if that first part goes fine do I update the UI with the result in an undoable fashion, using the above. I'm not sure there's a better way.
--
Shane Stanley <email@hidden>
'AppleScriptObjC Explored' <www.macosxautomation.com/applescript/apps/>
_______________________________________________
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