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: Luther Fuller <email@hidden>
- Date: Thu, 04 Apr 2013 12:24:48 -0500
On Apr 4, 2013, at 11:29 AM, Jim Skibbie wrote:
Here is what I'm suggesting as a workaround to your scenario:
calling.app:
property hostAppl : "called"
on
run try launch
application hostAppl tell
application
hostAppl to
theHandlerFormerlyKnownAsRun()
-- instead of on run, move the contents to its own handler tell
application
hostAppl to
doSomethingElse()
-- comment out and see what happens tell
application hostAppl to
quit on error
errText number
errNr activate me "CallingApp Error = " &
errNr & return &
errText tell me to
display dialog the
result buttons {"OK"}
default button 1 end try end
run
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