Re: Launching one Applescript app with another Applescript app fails in OS X 10.8
Re: Launching one Applescript app with another Applescript app fails in OS X 10.8
- Subject: Re: Launching one Applescript app with another Applescript app fails in OS X 10.8
- From: Jim Skibbie <email@hidden>
- Date: Thu, 04 Apr 2013 18:37:09 +0000
- Thread-topic: Launching one Applescript app with another Applescript app fails in OS X 10.8
I feel your pain. It's still a bug, and I reported it as such. Does anyone responsible for Applescript peruse this list?
What I came up with is certainly a work-around for my immediate situation, and while not ideal, did get me through the issue and on to other things.
As another kludgey option, what if you made two versions of your application. One the clickable version with the run handler that the user is aware of, and another one without the run, as the 'helper app'? You could even make your helper app act like an agent
so that it wouldn't show in the Dock and no one would really know it was running. Maybe then you don't need to even worry about quitting it. Again, none of this is ideal at all… just throwing it up there to see if it sticks.
Good luck!
On Apr 4, 2013, at 12:24 PM, Luther Fuller wrote:
> But this will not work for me.
> My main application (which is called by a calling script) must have the ability to 'run' when double-clicked. I can't do away with the run handler. The only fix is to correct the 'launch' command so that it no longer sends the unwanted and erroneous
'run' event.
>
> How do we get Apple's attention ? Is there a bug in Apple's operating structure that is short-circuiting our bug reports ? And to whom do we report that bug ?
|
_______________________________________________
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