Hi,
In an AppleScript script, which calls several apps, there is a call to a Perl droplet.
After running, MacPerl sits there, and eventually an Apple event times out, breaking
the chain.
I have put MacPerl::Quit(1) at the end of the Perl script, to no effect.
MacPerl::Quit(2) unloads MacPerl, bu
At 12:12 pm +0200 7/10/03, Louis Pouzin wrote:
In an AppleScript script, which calls several apps, there is a call
to a Perl droplet. After running, MacPerl sits there, and
eventually an Apple event times out, breaking the chain.
I have put MacPerl::Quit(1) at the end of the Perl script, to
--On Tuesday, October 7, 2003 12:12 PM +0200 Louis Pouzin
<[EMAIL PROTECTED]> wrote:
Hi,
In an AppleScript script, which calls several apps, there is a call to a
Perl droplet. After running, MacPerl sits there, and eventually an Apple
event times out, breaking the chain.
I have put MacPerl::Quit
Martin,
Your way sounds like a better approach. I'll try it for new scripts. In the present
case I had existing scripts I wanted to aggregate with minimum change.
Thanks a lot.
- -
On Tue, 7 Oct 2003 15:59:22 +0200, Martin Buchmann wrote:
>maybe you can port the whole AppleScript to a MacPerl s
John,
I did what you said, and it worked perfectly. I haven't tried mode batch tho.
The one thing I haven't yet figured out is what command would close the output window
opened by MacPerl for various diags. Any idea ?
Thanks very much
- -
On Tue, 7 Oct 2003 14:06:33 +0100, John Delacour wrote:
At 12:56 am +0200 8/10/03, Louis Pouzin wrote:
John,
I did what you said, and it worked perfectly. I haven't tried mode batch tho.
The one thing I haven't yet figured out is what command would close
the output window opened by MacPerl for various diags. Any idea ?
tell application "MacPerl"
