Nice! I was terrified to just try and make the leap on my finished product
without asking about how it works first. I thought the standalone needed to
give a password to run the stacks. Now I realize how these work! Awesome!
--
View this message in context:
http://runtime-revolution.278305.n4.nab
Hi Andrew,
Your standalone will be able to access the stacks, but they won't be able to
make any changes to them that involves scripts, including setting scripts and
copying from or pasting objects to those stacks.
--
Best regards,
Mark Schonewille
Economy-x-Talk Consulting and Software Engin
So password protecting these stacks don't affect what happens when my
standalone opens one of them?
--
View this message in context:
http://runtime-revolution.278305.n4.nabble.com/Stack-Password-Protection-tp3728618p3728647.html
Sent from the Revolution - User mailing list archive at Nabble.com.
Hi Andrew,
You can set the password of a stack from the message box. The syntax is:
set the password of this stack to "foo"
Replace foo with your password. To remove the password, do this:
set the passkey of this stack to "foo"
set the password of this stack to empty
Select inclusions manually
