I would hope that would be the behavior. It would also make it harder for your stack to get borked by someone else. If I was trying to break that behavior I would try to put the code into a variable, encrypt the variable using the password, then set the script of the object to the encrypted version, although I don't know what algorithm LC is using.
On Thu, Dec 30, 2021 at 2:13 PM Tom Glod via use-livecode < use-livecode@lists.runrev.com> wrote: > Hi Folks, > > Today I found out that if I put a password on my stack, any code that sets > the script of an object in that stack receives an execution error when > running as standalone. > > Why is this so? > > And is there a workaround? > > Thanks, > > -- > Tom Glod > Founder & Developer > MakeShyft R.D.A (www.makeshyft.com) > Mobile:647.562.9411 > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > -- On the first day, God created the heavens and the Earth On the second day, God created the oceans. On the third day, God put the animals on hold for a few hours, and did a little diving. And God said, "This is good." _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode