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: Fri, 18 May 2007 12:24:39 -0700
- Thread-topic: Filemaker 8.5 stored applescript problem
>>Gary>> Ed, what you may be missing is the use of the AS 'comment' to preserve
the not-yet-compiled string "«event rdwrread»", which can then be reused while
testing.
OK, I think the reason I'm missing that is I work mostly in Script Editor
and Script Debugger and in those environments any time I compile a script
the raw AE codes get compiled to AppleScript, so the only way that I could
envision using this technique would be to edit the script, then, uncomment
the lines and save the uncompiled script to a text file and use load script,
or send it back to Filemaker.
I simply couldn't describe that process as being more efficient.
> For example, in Smile or Script Editor, if I type this...
> -- «event rdwrread»
> «event rdwrread»
> ...and then compile, I will get this:
> -- «event rdwrread»
>read
> Since the word 'read' replaced the string '«event rdwrread»' on the
un-commented line, I can easily copy/paste it from the comment to test again.
Right, so the part I wasn't getting was how you would test it after that
copy and paste because, in Script Editor and Script Debugger, a compile is
required to run (test) the script, and that compile "fixes" the raw codes
again.
Of course if you editing scripts entirely within Filmaker's own script
editor (which I've never done) you may get a different behavior.
>>Dave>>Whoa. Yeah, I see what you mean now. That really sucks. I mean, by
its very definition, the ³containment hierarchy² should prevent this type of
thing.Have you ever seen this happen in any other app, or is it possible
that FMI just screwed up their AS implementation?
In Mac OS 7-9, HyperCard and FaceSpan, AppleScripts run from inside the
program behaved the same way. I don't know of any other OS X apps.
If you used Scripter, there was a menu choice at the top of every script
labeled something like "Terminology" that worked the same as "using terms",
long before the "using terms" construct was added to the language.
And I don't think it's screwed up, I think it's designed that way in the
name of "efficiency."
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