Re: Sudden unusual behaviour with tell app commands
Re: Sudden unusual behaviour with tell app commands
- Subject: Re: Sudden unusual behaviour with tell app commands
- From: "Marc K. Myers" <email@hidden>
- Date: Fri, 14 Sep 2001 13:51:05 -0400
- Organization: [very little]
>
Date: Fri, 14 Sep 2001 13:26:06 -0500
>
Subject: Re: Sudden unusual behaviour with tell app commands
>
From: "Bob.Kalbaugh" <email@hidden>
>
To: "email@hidden"
>
<email@hidden>
>
>
on 9/14/01 10:13 AM, John W Baxter at email@hidden wrote:
>
>
> It's probably easiest to develop with the target applications running.
>
>
Now, wait a minute guys. Please help me to clear this up, once, and for all.
>
>
Are yuns (<-- pittsburghese) saying that is the normal behaviour when
>
compiling new scripts from Script Editor? I've always thought that as long
>
as you were using the exact name of the application, a script would compile
>
via check syntax (not run) whether the app was running or not...that
>
Script Editor knows where to find it. In fact, I'd swear by this because the
>
only times I've ever been asked to locate an app (OMM) is when I've
>
incorrectly spelled the name. Could it be that for all this time, I've
>
inadvertently had the associative apps running?
No, it's just that you've been lucky. Sometimes Script Editor can find
'em and sometimes it can't. One sure (so far) way of having Script
Editor find your application is to put the complete path to the
application in your tell statement instead of just the name. Just don't
forget to set it back to just the name when you're done developing the script!
Marc K. Myers <email@hidden>
http://AppleScriptsToGo.com
4020 W.220th St.
Fairview Park, OH 44126
(440) 331-1074
[9/14/01 1:49:58 PM]