Re: Saving a property after running a script remotely
Re: Saving a property after running a script remotely
- Subject: Re: Saving a property after running a script remotely
- From: Paul Berkowitz <email@hidden>
- Date: Wed, 11 Sep 2002 07:44:31 -0700
On 9/11/02 4:41 AM, "John Delacour" <email@hidden> wrote:
>
At 8:20 pm -0700 10/9/02, Paul Berkowitz wrote:
>
>
> I have discovered that it's very difficult to save a property in a script
>
> being run by another script. I wonder if anyone knows a good, reliable
>
> method. Here's my set-up: [...]
>
>
>
I have never discovered that and I don't discover it now. If I run
>
"master" from the Script Menu (having the master/slave pair in my
>
Scripts folder) then this works as expected. The property is updated
>
and saved even if the window of "slave" is open in Smile.
You'd think I was making this up, or I didn't know how to script, from the
way you people are writing back..
I'm reporting something that may perhaps affect only large scripts - I've
noticed that they can take a while to "unwind". The Main Script is 100K.
I believe you that your little mini-scriplets here work as they should. I
thought my scripts should have too, and was puzzled that they didn't. But
they didn't, at least not reliably. If no one's interested, OK. Maybe you'll
never run into this if you don't write long scripts.
No one seems to believe that I know what I'm doing. All right. John suggests
that I do what I'm already doing, and that it works fine for his 10-line
scripts. Fine. That's interesting, in that it confirms it _should_ work. Or
I should log out and log in. No, I won't release scripts that require that
people log out and in every second time they use them, thanks. Andy advises
me to 'run script' without loading it. Yes, that's what I was doing after
the first paragraph, as I stated. That was in my message. Emmanuel suggests
'get' (current date) which isn't necessary with current date, unlike other
date compilations, or getting all my users to run the scripts in Smile.
What I'm still not certain of is whether the problems I'm getting are
arising only in the context of the new Script Menu, or not. The main script
seems to be "unavailable" for a short period at the end. There is something
a little odd in how SystemUIServer, which runs it, "releases" scripts. My
trigger script in the Entourage script menu is not finding the real main
script in Script Menu at the end. The whole reason for this setup is to be
able to run it from an Entourage schedule if desired, or directly from
Script menu. (It deals with another app as well as Entourage and has to be
available to be run from outside Entourage.)
If I find that it works reliably when the main script is an applet, would
anyone want to know?
--
Paul Berkowitz
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.