On 16/8/00 7:30 am, David Bovill <[EMAIL PROTECTED]> wrote:
> Trying to set the password of a stack with a script. Problem is that it seems
> that the user can still edit scripts until the stack is saved, closed and
> re-opened. Not getting very far with trying to do this in a script.
>
> Here is the script that I am trying to define to add a password to a stack and
> then lock it so you can't look at the scripts after it has been called. This
> one is slow, but works except for the fact that the stack does not open - too
> ealy after closing?
>
> on lockStack newPassword
> set the password of this stack to newPassword
> save this stack
> put the fileName of this stack into myFilename
> close this stack
> open stack myFilename
> answer the result
> end lockStack
>
> Is there a better way of doing this?
That handler works here, though it doesn't lock the scripts because the
stack is not removed from memory. You need to delete the stack or close it
with destroyStack to remove it from memory then reopen it. Of course, this
script can't be part of the stack.
Regards,
Kevin
Kevin Miller <[EMAIL PROTECTED]> <http://www.runrev.com/>
Runtime Revolution Limited (formerly Cross Worlds Computing).
Tel: +44 (0)131 672 2909. Fax: +44 (0)1639 830 707.
Archives: http://www.mail-archive.com/metacard%40lists.best.com/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to <[EMAIL PROTECTED]>, not this list.
