Meatball protected stacks :-)

[Peter Haworth]

I'm willing to give it a go.  Is there data other than than scripts,
inspector palette properties, and custom properties that should be options?

In the meantime, there are some custom property values that I just don't
want to hardcode in scripts.  I guess my only option is to encode them
somehow.

Pete
lcSQL Software <http://www.lcsql.com>



On Fri, Jul 6, 2012 at 1:24 PM, Richard Gaskin
<ambassador at fourthworld.com>wrote:

> Peter Haworth wrote:
>
> > I was somewhat surprised to find that it is possible to access
> > the Inspector palette for any objects in a password protected
> > stack without supplying the password.  I guess it's OK but there
> > could be information stored in custom properties that you would
> > not want a user to see.  Now I know, I guess I can just avoid
> > that situation.
>
> Password protection affects only scripts.
>
> I had thought there was a request to extend that to optionally cover other
> data such as custom properties, but I couldn't turn it up in the RQCC.
>
> If you can come up with syntax for that it may make a good proposal.
>
> --
>  Richard Gaskin
>  Fourth World
>  LiveCode training and consulting: http://www.fourthworld.com
>  Webzine for LiveCode developers: http://www.LiveCodeJournal.com
>  Follow me on Twitter:  http://twitter.com/**FourthWorldSys<http://twitter.com/FourthWorldSys>
>
>
> ______________________________**_________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/**mailman/listinfo/use-livecode<http://lists.runrev.com/mailman/listinfo/use-livecode>
>