Encrypted stack behavior...etc.

[Barry Levine]

Okay, folks. I'd better put a stop to this thread I started. The 
problem was not the encryption but the fact that I was attempting to do 
something that isn't permitted in an encrypted stack ("copy"). And that 
problem was brought about by my misunderstanding of the hierarchical 
nature of a group's objects' property inheritance (*whew* say -that- 
fast!). Once I realized that I had to make the group visible before I 
could make the images contained therein invisible and visible (without 
having to ungroup them - and that was a relief), the need to copy or 
clone the individual images simply went away. Therefore the encryption 
stays in and my stacks are secure.

Richard Gaskin offered a suggestion that I separate the user interface 
from the code using an encrypted substack for the code (with a "start 
using" command in the openStack handler of the main stack). This would 
provide a means (going further) to utilize libraries of common code to 
which short handlers in the interface elements would refer. It might 
also, it seems, remove some of the restrictions (copy, etc.) other wise 
present in an encrypted stack. As my days coding Business Basic have 
shaped my coding "style", so to speak, I have much to internalize in 
the way of Rev's object-oriented, inheritance-based approach (in spite 
of 8 years working with HyperCard). However, with the right tools (Rev) 
and support (this list), I know it will happen.

Thanks to everyone,
Barry

On Wednesday, Sep 3, 2003, at 09:57 America/Denver, Mark wrote:

> Subject: Re: Encrypted stack doesn't behave properly - oops; yes it 
> does.
> From: Mark Talluto <revlists at canelasoftware.com>
> To: use-revolution at lists.runrev.com
> Reply-To: use-revolution at lists.runrev.com
>
>
> On Tuesday, September 2, 2003, at 11:55 PM, Scott Rossi wrote:
>
>> 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.
>>
>>
>
> You are right Scott.  Once it is set, it is set.  This is unless you
> set it to empty and save it.
>
>
> Best regards,
> Mark Talluto
> http://www.canelasoftware.com