Encrypted stack doesn't behave properly - oops; yes it does.

[Scott Rossi]

On 9/2/03 9:42 PM, "Mark Talluto" <revlists at canelasoftware.com> wrote:

>> All I want to do is protect my code from view if someone tries to
>> examine my stacks with Rev or with TextEdit. How can I do this?
>> Obviously, this is not the application but a secondary stack (not
>> sub-) whose data gets altered and saved during runtime. I can't ask
>> the user to provide the password as I want to keep it a secret.

> Set the passkey when the stack is opened.  Then set the password before
> saving the data stack again.

I don't believe you need to set the password after setting the passkey.  The
passkey allows you access to the stack during the current editing session;
to remove a password from a stack you'd need to set the password to empty.
Thus, once you set the passkey of a stack, the stack can be edited as
needed, saved, and closed.  Once it is closed, it will be protected as
before.

Regards,

Scott Rossi
Creative Director
Tactile Media, Multimedia & Design
-----
E: scott at tactilemedia.com
W: http://www.tactilemedia.com