compiler directive, was (Follow-up on appletalk volume mounting)
compiler directive, was (Follow-up on appletalk volume mounting)
- Subject: compiler directive, was (Follow-up on appletalk volume mounting)
- From: "Arthur J Knapp" <email@hidden>
- Date: Fri, 19 Jan 2001 11:56:22 -0500
>
Date: Fri, 19 Jan 2001 08:25:30 -0500
>
From: "Stephen Gross" <email@hidden>
>
Subject: Re: applescript-users digest, Vol 2 #245 - 13 msgs
>
> Date: Fri, 19 Jan 2001 00:07:35 -0600
>
> Subject: Re: Follow-up on appletalk volume mounting
>
> From: JollyRoger <email@hidden>
>
> on 1/18/2001 10:00 AM, Stephen Gross at email@hidden wrote:
>
>
>
> > Can I force the script editor to recognize a
>
> > command as associated with one scripting addition and not another?
>
> If the scripting addition were an application, you could just tell that
>
> application. The only other way I know of is to disable the problem
>
> scripting addition.
>
Right, so the next question is: is there a way to disable the scripting
>
addition
>
within the script? Some sort of compiler directive, I mean?
Let's pretend that there are two Scripting Additions that have
a "display dialog" command. The following would ensure that Apple's
command was the one used:
on DisplayDialog(prompt_text, default_answer)
run script ,
("+event sysodlog; \"" & prompt_text & ,
"\" default answer \"" & default_answer & "\"")
end DisplayDialog
DisplayDialog("'syso' is the suite", "'dlog' is the command")
Unfortunately, the "run script" command is notoriuosly slow
if you have to use it alot.
P.S. The characters preceeding and following "event sysodlog"
are option-backslash and shift-option-backslash,
respectively. (Take that, mail server).
--
{
Arthur J Knapp, of STELLARViSIONs ;
http://www.STELLARViSIONs.com ;
mailto:email@hidden ;
"...it's not my birthday,
it's not today..."
}