Re: Finding Terminology Conflicts
Re: Finding Terminology Conflicts
- Subject: Re: Finding Terminology Conflicts
- From: Arthur J Knapp <email@hidden>
- Date: Mon, 15 Apr 2002 20:55:46 -0400
>
Date: Fri, 12 Apr 2002 10:16:19 +1000
>
From: Malcolm Fitzgerald <email@hidden>
>
Subject: Finding Terminology Conflicts
>
Is there any way to identify potential terminology conflicts between
>
AppleScript and another application? I've just spent a day watching
>
in horror as a stable script library became like cerberus, blocking
>
my path, and whenever it moved a little I could see that hell was
>
behind it. All the more suprising because the handler that grew heads
>
was by that bright, young chap, Knapp. ;-)
I hate that guy...
Actually, I was surprised at how accurate your description was of
nearly every handler I have ever written. ;-)
Script Debugger can help with examining raw codes, though not for
free. Someone once did post something about compiling a script,
removing the application?, and then opening the script back up again
to get at the raw codes, (or something like that).
>
It turned out that there was a terminology conflict between FMPro and
>
Applescript over "record". So:
>
>
tell "filemaker pro"
>
the clipboard as record
>
-- can't make the clipboard into a record
>
-- it is the wrong data type
>
The problem was that filemaker was claiming "record", so that it was
>
being interpreted as <<class cRow>> (filemaker record) instead of
>
<<class reco>> (applescript record) but both use the same terminology.
The "the cliboard" command, (originally written by the great Jon Pugh),
has a secret bit of functionality: you can specify the "as" parameter as
a four character code:
the clipboard as "reco"
>
The code had been running previously without error, I had added a new
>
handler to the script library so it had been re-compiled. I've been
>
working with this script library for weeks, tweaking, changing,
>
re-building... So, why now? I've been using the same development
>
environment all along, what is it that makes the code decide it wants
>
to use FMPro's library instead of Applescript's?
One of the mysteries of our times... ;-)
The compiled code in an AppleScript is incredibly persistent, and
subject to all kinds of bizzare behavior. Did you add the new handler
"above" the previous handlers? Perhaps it has something to do with the
order in which the compiler processes certain terminologies.
{ Arthur J. Knapp, of <
http://www.STELLARViSIONs.com>
<
mailto:email@hidden>
try
<
http://www.LateNightSW.com/>
on error number -128
end try
}
_______________________________________________
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.