Finding Terminology Conflicts
Finding Terminology Conflicts
- Subject: Finding Terminology Conflicts
- From: Malcolm Fitzgerald <email@hidden>
- Date: Fri, 12 Apr 2002 10:16:19 +1000
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. ;-)
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
end tell
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 solution was found in The Practicing AppleScripter's SDK (a
punching bag, a box of tissues and a finger of irish whiskey). Check
the ASLG for distributors.
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? (and was there a way
to read raw codes? I know that Smile will translate to raw code, but
I want to read compiled code as raw code.
--
--
Malcolm Fitzgerald email@hidden
Database Manager
http://www.asauthors.org
The Australian Society of Authors ph: 02 93180877 fax: 02 93180530
_______________________________________________
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.