Ah, now I see what you mean. It is true that Quicksilver does not save persistent values when running a script, because the method it uses is to read the script's code and then run that code itself, rather than simply telling the operating system to execute the script. However, for this script (at least as downloaded my me today) nothing in your global variables makes a whit of difference to the execution of the code. As I said in my reply on macosxhints:
"I did misunderstand you. However, the script works exactly the same when run via Quicksilver as it does when run via any other method I have tried. It does define some variables that would be persistent, but nothing that persists does anything that matters. Also, since this uses GUI scripting, the best general practice would be not to remember any values across executions, since the user may change something unexpected between executions." On Sep 10, 6:51 pm, philgroups <[email protected]> wrote: > Hi Sesquipedalian, > > I'm posting in response to this hint on > macosxhints.com:http://hints.macworld.com/article.php?story=20100904050851695 > > Applescripts run across restarts of Quicksilver, but, for me, QS never > remembers the contents of the global variables in the scripts (whether > QS is restarted or not). I get the same results from a trigger and > from the QS window. > > However, I would love for this to work! Cheers, philgroups.
