Re: Filemaker 8.5 stored applescript problem
Re: Filemaker 8.5 stored applescript problem
- Subject: Re: Filemaker 8.5 stored applescript problem
- From: "Stockly, Ed" <email@hidden>
- Date: Wed, 16 May 2007 10:56:52 -0700
- Thread-topic: Filemaker 8.5 stored applescript problem
>M> 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.
I'm a little lost here, are you saying copy and paste your comment into your
script every time you save?
>>>>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 saying putting the read write command in a handler to avoid the
terminology conflict, that would not work in this case, because handlers in
scripts launched from within filemaker are also executed as commands to
filemaker, and I believe the same is true for libraries used from those
scripts (but I'm not sure about that part).
Clearly the simplest, easiest, appleScriptiest solution is to enclose the
commands in a Finder or System Events tell. In this case I would argue that
it's not noticeably less "efficient" or slower than the alternatives, unless
you're executing hundreds or thousands of OSAX calls.
>>>If you're doing more than one liners or testing, having a general purpose
write function is probably a handy thing.
That's definitely a good idea, even if you're not trying to avoid
terminology conflicts.
Handlers are our friends.
ES
_______________________________________________
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