Re: Explicit run handler usage
Re: Explicit run handler usage
On 27 Apr 2010, at 21:56, Christopher Nebel wrote:
>
> "Always" is a long time. I'd rather people explicitly subclassed NSObject, but the implicit subclassing will continue to work for some time. Worst case, you'll start getting warnings at some point in the future.
>
Thanks.
>> 2. if I change the code to use an explicit run handler (version 2) the run handler does not get called. Why?
>
> Because calling terminology-named methods (such as "run") through the bridge isn't supported. Check the Xcode log and see if you're getting a warning about it; if you're not, I have some work to do.
Rest easy. Calling the run method through the bridge does indeed generate "unrecognized selector sent to object".
What fails silently is calling the run handler of a bundle loaded script (using [[NSBundle mainBundle] loadAppleScriptObjectiveCScripts];) from an AppleScript application delegate.
The delegate's outlet references the script object but it does not respond to run handler execution requests.
Presumably there is an NSObject proxy representing the AS script object that, as we know, excludes the run method.
Regards
Jonathan Mitchell
Developer
http://www.mugginsoft.com _______________________________________________
Do not post admin requests to the list. They will be ignored.
applescriptobjc-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden