Re: Workaround for terminology conflicts
Re: Workaround for terminology conflicts
- Subject: Re: Workaround for terminology conflicts
- From: Walter Ian Kaye <email@hidden>
- Date: Wed, 10 Sep 2003 03:24:58 -0700
At 11:34a +0200 09/10/2003, HOnza Koudelka didst inscribe upon an
electronic papyrus:
Hi!
I am looking for opinions about using "System Events" versus
"Finder" for working around terminology conflicts.
For example, Finder and FileMaker Pro don't interpret the "kind"
keyword equally.
To prevent terminology conflicts and also to avoid creating new
global terms where not needed, we have adopted the Finder's
interpretation of the word "kind" in our scripting addition.
The problem is that scripts using this term don't compile correctly
in FileMaker Pro, and so they don't work. As a workaround, we
recommend to our users to enclose the critical command(s) in the
using terms from application "Finder" block.
I am wondering what other people think about this workaround. Is it
the right one? Shouldn't we use "System Events" rather than
"Finder"? What do you think?
Well, FileMaker cannot even handle the 'read' command, despite there
being no FMP terminology for 'read'. I would just make sure there are
no conflicts in Script Editor (and Smile, Script Debugger, and
FaceSpan 4.0), and not worry about FileMaker -- leave any FMP
conflicts to the folks in The Wedge to fix.
Do make sure your raw event codes are unique; then your users could
use a workaround of entering the raw codes in case of conflict within
FMP.
-Walter
_______________________________________________
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.