Forcing a script to open in Classic
Forcing a script to open in Classic
- Subject: Forcing a script to open in Classic
- From: "Scott P. Richert" <email@hidden>
- Date: Sat, 25 Jan 2003 16:11:31 -0600
I've recently taken a script that I've been running on OS 9, to
generate PS files in QXP and then distill them to PDFs, and have
created an AppleScript Studio app based on it. Of course, as I noted
in posts to the list ("Scripting QuarkXPress from OS X"), I couldn't
target the print command in QXP directly from X (it would time out), so
I've had to move what I could to the ASStudio app and leave the rest
(anything directly target QXP or Acrobat Distiller) in a stay-open
applescript that runs in Classic.
Let's call the app "PDF Generator" and the stay-open Classic
applescript "Subroutines." Everything works great if I doubleclick
Subroutines in the Finder (it opens in Classic) and then open PDF
Generator. What I'd really like to do, however, is have PDF Generator
launch Subroutines when PDF Generator is launched. The following
script works (and yes, I have stored Subroutines inside the PDF
Generator package for portability--it works just fine):
on will finish launching theObject
set subroutinesPath to (path to me as string) &
"Contents:Resources:Subroutines.app"
tell application subroutinesPath
launch
end tell
end will finish launching
The problem, however, is that Subroutines launches in X, not in
Classic. Doubleclicking, as I've noted, opens it in Classic; calling
it from AppleScript opens it in X. (I've verified this in Script
Editor as well.)
How can I call Subroutines from AppleScript and force it to open in
Classic?
Scott P. Richert
Executive Editor
Chronicles: A Magazine of American Culture
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.