Re: solutions to scripting addition terminology conflicts
Re: solutions to scripting addition terminology conflicts
- Subject: Re: solutions to scripting addition terminology conflicts
- From: Paul Berkowitz <email@hidden>
- Date: Fri, 25 Jan 2002 21:49:56 -0800
On 1/25/02 9:10 PM, "email@hidden" <email@hidden> wrote:
>
I made a copy of an AppleScriptable application, named it "Terminology", and
>
removed its aete dictionary resource. I then created a new aete, with the
>
single event "tock", which had the same event code as "the ticks" from Jon's
>
commands.
>
>
I then wrote and ran this script:
>
>
using terms from application "Terminology"
>
tock
>
end using terms from
>
>
--> Result: 15727342 (what you'd expect from 'the ticks')
This is quite fascinating. When you say you created a new aete, you mean for
this copied app you've re-named "Terminology"? Is there any reason then why
you can't use terms from existing scriptable apps without a tell block to do
things? Why do those apps have to be "told" and 'application "Terminology"
doesn't have to be told? There's obviously something about the raw code for
'tock' (i.e. 'the ticks') that makes it work system-wide, which is not true
for regular apps. I guess that's obvious, although I have no idea what makes
osaxen "system-wide" in effect. So it's just that the word 'tock' has no
meaning other than as a variable outside this construct. OK. yes, this does
seem brilliant. Bravo.
You'd provide just the one app "Terminology" for all such osax commands? Is
the "copying a scriptable app" part a hack that would work any differently
if you made a custom app with its own aete?
--
Paul Berkowitz