On 23/08/2013, at 10:53 AM, Bradley O'Hearne <[email protected]> wrote:
> Just to clarify -- it is broken in that it's behavior doesn't specifically
> <what> instead of doing specifically <what>?
The actual bug was logged on AppleScript behavior, so excuse the diversion -- I
suspect you can extrapolate. Traditionally the launch command was used to
launch an app but not make it active, thus avoiding splash screens and new
documents that appeared with the run command, or where there was no explicit
run/launch command. In 10.5 launching in the background was made the default
behavior, so launch was rarely needed. However, if you saved an AppleScript
application, and launched it from a separate script or app using the launch
command, it would launch but not call its run handler. At some stage, possibly
as far back as 10.7, this changed, and launch now behaves exactly the same as
run ('oapp') in such cases. I don't think the change was the result of anything
done to AppleScript, so I suspect it's something further upstream, in AppKit or
launch services.
--
Shane Stanley <[email protected]>
'AppleScriptObjC Explored' <www.macosxautomation.com/applescript/apps/>
_______________________________________________
Cocoa-dev mailing list ([email protected])
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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [email protected]
