Re: Filemaker 8.5 stored applescript problem
Re: Filemaker 8.5 stored applescript problem
- Subject: Re: Filemaker 8.5 stored applescript problem
- From: Malcolm Fitzgerald <email@hidden>
- Date: Wed, 16 May 2007 11:48:18 +1000
On 16/05/2007, at 10:04 AM, Matt Deatherage wrote:
On 5/16/07 at 6:22 PM, Tim Mansour <email@hidden> wrote:
It's more efficient if we don't use the Finder, and we also don't have
to worry if it's hung or busy. Surely any "readability" issue could be
easily solved with a comment:
tell application "FileMaker Pro"
-- «event rdwrread» is standard additions "read":
set cell "FileContents" to «event rdwrread» alias theFilePath
end tell
This is true, and this works within FileMaker's spartan AppleScript
dialog box.
However, if you develop your scripts in Script Editor or (my choice)
Script Debugger for easier debugging, you find that the AppleScript
decompiler changes the raw event codes *back* into the "read" and
"write" English words because they match terms in the Standard
Additions
dictionary. Therefore, on your next compile and on every subsequent
change, you have to replace the terms with the raw event codes or you
get the compilation errors again.
It can be a nuisance, but comments don't get compiled, so you have them
there for re-use if/when you can't get them out of the way. By
"getting them out of the way" I mean having the read or write
functionality stored in a handler or script library. If you're doing
more than one liners or testing, having a general purpose write
function is probably a handy thing.
malcolm
_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users
This email sent to email@hidden