Re: Called script won't store property
Re: Called script won't store property
- Subject: Re: Called script won't store property
- From: Doug McNutt <email@hidden>
- Date: Sun, 27 Feb 2005 21:28:53 -0700
At 23:34 +0000 2/27/05, kai wrote:
>When you open a script application manually, it is automatically saved when it quits. This evidently doesn't happen with the run script command, which I suspect is similar to running a copy in memory.
Does that suspicion mean that the run script behaves like a "source" command in tcsh or the equivalent in bash?
Can the script being "run" have a name conflict with a variable in the calling script? Must a script expecting to be called be careful to use "my" directives for localization?
Can the called script modify a property defined in the calling script? A global?
There was a question about c-like #includes recently and there was no real solution. Is the called script really being included as opposed to being executed as a stand-alone application? Does "running a copy" imply that the called script is getting recompiled?
Do properties in the called script revert to the original "missing value" as it is executed or does it remember the value set when it was last double-clicked?
Is there a good way to distinguish, in a script, whether it was "run" or double clicked? Is it different if , instead or "run script", you "tell application called_Script to run" ?
Anyone have a definitive reference to offer? Suspicion is NOT the best basis for bug free code.
--
--> If you are presented a number as a percentage, and you do not clearly understand the numerator and the denominator involved, you are surely being lied to. <--
_______________________________________________
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