I thought that setting the password on a stack stopped anyone getting
at the scripts but otherwise left the stack modifiable. However, I
just put a password on a stack that creates grouped image + text
objects on the fly as and when needed and found that this no longer
worked with the stack password protected. As soon as I removed the
password (or used the "set the passkey of this stack" command), it
worked again!
This is a potential problem since I want to protect the scripts (and
any externals, as per licence conditions), but can't do so if the
stack needs to create objects on the fly!! Alternatively, I have to
get the stack to unlock itself on the fly as and when needed by using
the "set the passkey of this stack" command - again, a bit messy!
So what does password protecting a stack inhibit:
- creating new objects (using "copy" and "paste")?
- creating/updating object properties?
- modifying existing scripts?
- creating new scripts/handlers on the fly?
etc.
This was tested with the latest build (downloaded a couple of days
ago) of MC 2.3.2 for PowerPC Mac.
Peter
--
--------------------------------------------------------
Peter Reid
Reid-IT Limited, Loughborough, Leics., UK
Tel: +44 (0)1509 268843 Fax: +44 (0)870 052 7576
E-mail: [EMAIL PROTECTED]
Web: http://www.reidit.co.uk
Archives: http://www.mail-archive.com/[email protected]/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to <[EMAIL PROTECTED]>, not this list.
