Re: Dialog from script application displays raw codes (was: no subject)
Re: Dialog from script application displays raw codes (was: no subject)
- Subject: Re: Dialog from script application displays raw codes (was: no subject)
- From: Peter Bunn <email@hidden>
- Date: Sun, 27 Aug 2006 11:38:30 -0500
Earlier today, kai wrote:
>One way of doing this is to use the run script command to act upon a text
>script (which will not yet have been compiled). When the terms contained
>in the text are encountered, the compiler is called upon to compile them
>as executable code - so that the script can be executed in the normal way.
>For this, the relevant dictionaries need to be accessed - after which the
>required terms become available to our main script.
>
>Such a statement can be added at the beginning of the script, and needs no
>specific commands. Usually something like this should suffice (to access
>Finder's terms):
>
>----------
>run script "tell application \"Finder\"
>end"
>----------
Out of curiosity, would this constitute a usable way of circumventing a
'double tell' or equivalent in a more complicated text script? Or would
the added compile time at run time kill it as such?
Or am I misunderstanding the effect?
Thanks.
Peter B.
(Just another dead cat.)
-----
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden