Reminder: objects cannot be copied when stack is password-protected!!! Even in a standalone. Grrrrrr....

Dave dave at
Wed Feb 27 05:47:04 EST 2008


I'm not sure I follow this, are you saying that you can't set the  
passkey from another stack and do your copy thing?

I guess setting the passkey in the stack itself is ok if you can hard- 
wire your password/passkey, but what if you can't use a literal?

All the Best

On 26 Feb 2008, at 23:32, Josh Mellicker wrote:

> Once upon a time, a programmer was working on a project, with many  
> handlers that copy objects, for example, copy groups into groups to  
> form scrolling groups, and everything was working great, and the  
> programmer was very happy, and then, as a last step, he password  
> protected the stack, then, the next day...
> BLAMO!!!! Strange, bizarre things happened. Groups would not copy.  
> Death and destruction reigned. Monitors came crashing out windows.  
> Expletives burned the ears of innocent bystanders.
> This programmer then leapt off a cliff, ending it all.
> MORAL: If he had only put a single line of code:
> set the passkey of this stack to "swordfish"
> in the preOpenStack script, all would be fine.
> Please, tell your kids about "passkey", don't let them suffer a  
> similar fate!
> _______________________________________________
> use-revolution mailing list
> use-revolution at
> Please visit this url to subscribe, unsubscribe and manage your  
> subscription preferences:

More information about the Use-livecode mailing list