Encryption inconsistency, not a "bug"

[Barry Levine]

However, objects may be cloned. Why cloning doesn't have the same 
restriction as a "copy", I haven't a clue. In any case, I now stand 
corrected (and properly chastised - mea culpa). I had been hoping to 
use the copy or clone command to permit image objects in a hidden group 
to be shown or hidden individually. However, cloning an object in a 
group seems to add that new object to the group. Therefore, I can't 
show or hide it individually. I guess I'll have to -not- group the 
images and manipulate them individually. *sigh*

Barry

On Monday, Sep 1, 2003, at 18:12 America/Denver, Scott wrote:

> Subject: Re: no encryption bug - extremely hidden feature ;-)
> From: Scott Rossi <scott at tactilemedia.com>
> To: <use-revolution at lists.runrev.com>
> Reply-To: use-revolution at lists.runrev.com
>
>>> The Rev docs say that encryption is supposed to prevent users from
>>> changing the stack
>>> but that scripts are unaffected. Is this a bug?
>>
>> This is a rather undocumented(?) feature.
>
> Well, not exactly undocumented:
>
> "If the password is set, the stack¹s scripts cannot be modified, its
> password cannot be changed, and objects cannot be copied."