Saving a standalone

[Ken Ray]

Shari,

Actually, you can protect a stack as well as a standalone. Set the
cantModify to true, give it a password and save it. The only thing someone
with MC will be able to do is open your stack and view the cards - they
won't be able to view or change scripts, and even if they move objects
around, it won't be saved due to the cantModify. The scripts are also
encrypted so that text editors won't be able to see anything but garbage.

The only additional protection a standalone offers is that someone with MC
can't just "open" a standalone and view the cards.

Ken Ray
Sons of Thunder Software
Email: kray at sonsothunder.com
Web Site: http://www.sonsothunder.com/

----- Original Message -----
From: "Shari" <gypsyware at earthlink.net>
To: <metacard at lists.runrev.com>
Sent: Thursday, June 27, 2002 9:49 AM
Subject: Re: Saving a standalone


> >Recently, Simon Lord wrote:
> >
> >>  Is it possible to have a standalone make changes to itself and
> >>  actually save those changes?
> >
> >Nope.  You can only edit/save (non-standalone) stacks.  You can get close
to
> >what you ask by keeping the bulk of your scripts in a stack and using a
> >small standalone engine to run the stack -- changes are save by the
engine
> >to the stack.
> >
>
>
> Doesn't that defeat the purpose of using a standalone?  Anything in
> the stack, can't it be opened etc. by anyone with Metacard?  The
> purpose of using a standalone besides convenience, is to protect the
> data, scripts, imports, etc. from anyone with prying eyes.  Yes you
> can script some protective things into a stack, but the whole purpose
> of having a standalone is for the extra protection it offers.
>
> --
> --Shareware Games for the Mac--
> http://www.gypsyware.com
> _______________________________________________
> metacard mailing list
> metacard at lists.runrev.com
> http://lists.runrev.com/mailman/listinfo/metacard
>