User Level and Password Protection

Ken Ray kray at sonsothunder.com
Wed Apr 17 14:57:01 EDT 2002


Rick,

Sure... sorry for being a little opaque. I believe someone on the list
earlier was using a stack to store images that he didn't want others who had
Revolution to be able to see (since they are copyright protected images).
Setting the password does not prevent someone from *opening* your stack; it
only prevents people from seeing your scripts. I was saying that there were
other methods necessary to prevent people from looking at card data that
could be implemented. But this doesn't seem to be needed in your case.

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

----- Original Message -----
From: "Richard Harrison" <harrison at all-auctions.com>
To: <use-revolution at lists.runrev.com>
Sent: Tuesday, April 16, 2002 11:49 PM
Subject: Re: User Level and Password Protection


> on 4/16/2002 11:47 AM, Ken Ray at kray at sonsothunder.com wrote:
>
> > Rick,
> >
> > You *can* set a password for your stacks to prevent people from looking
at
> > your scripts. (Look under the "password" property in the Transcript
> > Dictionary.) And you can set the "cantModify" of the stack to prevent
people
> > from adding or changing data in your stacks. What you need to do
manually
> > (if you need this at all) is to put something in to prevent certain
people
> > from *looking* at the data in your stacks - this would need a login
screen
> > or equivalent.
> >
> > Ken Ray
>
> Ken,
>
> Thanks for directing me in the correct direction.
>
> I'm not sure what you mean by something to prevent
> certain people from *looking* at the data in my stack.
>
> The only data they should be seeing is the data I want
> to show to them.  Other data is all in hidden fields.
> Could you be more verbose?
>
> Thanks,
>
> Rick
>
>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> http://lists.runrev.com/mailman/listinfo/use-revolution
>




More information about the use-livecode mailing list