Re: path to confusion
Re: path to confusion
- Subject: Re: path to confusion
- From: Christopher Nebel <email@hidden>
- Date: Wed, 16 Feb 2005 03:49:32 -0800
On Feb 16, 2005, at 1:54 AM, Håvard Graudo wrote:
To load my script libraries I use routines like this:
set theLib to "" & (path to application support) & "a script library"
load script theLib
It works most of the time. However if the script is triggered from a
"classic" application, the 'path to application support' then points
to the application support folder inside the classic system folder,
and not root/library/ ...
That's correct. When you "tell" a Classic application -- which
includes the possibly implicit "me" if you're running inside one -- you
get the Classic versions of the scripting additions, such as "path to",
and from its point of view, that *is* the application support folder,
because it only knows about the Classic system folder. That's sort of
the point of Classic. If you always want the "native" one, always tell
a native application -- "Finder" should serve this purpose well, and
will work on both 9 and X.
Emmanuel's suggestion of adding "from local domain" won't help here,
because the problem is that you're talking to the Classic "path to",
which has no idea that the domain parameter even exists, let alone
where the domains are. The domain parameter is useful for some things,
but not this.
--Chris Nebel
AppleScript Engineering
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden