Re: Second Call to Non-Stay-Open Script App Fails
Re: Second Call to Non-Stay-Open Script App Fails
- Subject: Re: Second Call to Non-Stay-Open Script App Fails
- From: "S. J. Cunningham" <email@hidden>
- Date: Wed, 04 Jun 2014 04:52:04 -0400
On Jun 4, 2014, at 4:27 AM, Shane Stanley wrote:
> On 4 Jun 2014, at 6:12 pm, S. J. Cunningham <email@hidden> wrote:
>
>> I thought the whole point of "launch" was to open an app without calling it's run handler.
>
> The launch command has been broken for many releases now -- it always calls the run handler. (Actually, the original point of launch was more to do with running apps without making them active, but the change to run/open behavior made that moot.)
Thanks, Shane. I suspected that :( Oh, well.
> If you're running Mavericks, script libraries are the logical alternative.
I'm a Snow Leopard die-hard. What I was trying to do was to use properties in a script library to pass data between "client" scripts to avoid reading and writing to separate files. As far as I can tell, l if I just load the script library, each client script get's it's own copy and a change to the library's properties is only seen by that client script. To do what I want, it seems the script library needs to be a stand-alone, stay-open app. I'm not sure what problems that will cause other than cluttering up the Dock, randomly becoming the frontmost application, and eventually dying from a memory leak or something :)
PS: I'm still trying to save up enough money to buy your book ;)
_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users
This email sent to email@hidden