On Apr 4, 2013, at 10:11 AM, Jim Skibbie wrote:
I should have mentioned that AppB (in my second example) has to be saved as a 'Stay Open' style app either through a script editor or with osacompile's '–s' flag.
Perhaps that is why you are getting a different result? I'd be curious to know if you can't reproduce the work-around.
I tried this, but got the same result (-609 error). Also, the unwanted 'run' handler in the CALLED script still runs. For me, this is a real problem. My called application has a run handler which initiates a long complicated handler. In order for my application to behave properly, this must be suppressed when 'launching' another handler.
The real bug here is that AppleScript no longer behaves as specified in "AppleScriptLanguageGuide.pdf". (and therefore is a serious bug!)
These work-arounds, even if they do work, do not change the fact that the behavior of AppleScript is no longer as specified. This bug must be fixed by Apple to restore the behavior of AppleScript to specification.
How do we convince Apple that this is a serious bug which requires an immediate fix ?
|