protecting images in a standalone
docmann at gmail.com
Fri Mar 18 21:07:49 CST 2005
Hello Jacque and thanks for the reply!
Actually, after reading so much about them on this list, the idea of
using custom properties to store the images was my first
consideration. (I even purchased Dan's e-book as a reference).
Although I may be wrong (most often the case), I just don't think it
would work with the volume of images I need to use ---> about 4500
images, all around 3-5K in size.
I guess I was just hoping that maybe there was a lib or external
available for Rev, with some sort of encryption scheme that could be
On Fri, 18 Mar 2005 20:44:39 -0600, J. Landman Gay
<jacque at hyperactivesw.com> wrote:
> You could put each image into a stack as a custom property. If the
> images aren't too large, you could put more than one in each stack. Then
> start using the stack, extract the custom property as needed, and load
> it into an image object on your main stack. If you password-protect the
> storage stack, the data content will be scrambled with the image content
> if anyone tries to look at it in a text editor. It would be disguised on
> casual inspection.
> Jacqueline Landman Gay | jacque at hyperactivesw.com
> HyperActive Software | http://www.hyperactivesw.com
> use-revolution mailing list
> use-revolution at lists.runrev.com
More information about the use-livecode