Re: persistant state: what is best technique?
Re: persistant state: what is best technique?
- Subject: Re: persistant state: what is best technique?
- From: Cal <email@hidden>
- Date: Tue, 16 Jan 2001 15:53:49 -0500
Michael Turner <email@hidden> wrote:
I am scripting Quark scripts, and am considering breaking one of my largish
scripts into several quickeys activated scripts. But if I do this, I need to
artificially preserve the state of one or two variables from script to
script. I can think of a couple ways to do this, but I don't like any of
them. Does anyone have a suggestion?
The cleanest way is to use ScriptBase, a database that allows you to
stash variable values in a systemwide place so all the scripts on
your computer have access to them. A single-user copy comes free
with Scripter, and individual (or inexpensive multiple) runtime
licenses are available if you need to run your scripts on other
computers. Check it out at
http://www.mainevent.com
Cal