There shouldn't be anything infuriating about it. You have a password protected stack. You set the passkey of that stack to your password value. You should then be able to access/copy objects from that stack.
The passkey stays in effect for the current editing session. When you close stack (or otherwise remove it from memory), your stack contents should not be accessible the next time you open stack. Passkey is temporary, password is persistent. Regards, Scott Rossi Creative Director Tactile Media, UX/UI Design On 4/14/15, 11:20 AM, "Dr. Hawkins" <doch...@gmail.com> wrote: >On Sat, Apr 11, 2015 at 5:26 PM, Scott Rossi <sc...@tactilemedia.com> >wrote: > >> If you set the passkey of the protected stack (to the password) before >> copying, you should be able to copy what you want >> > >This is getting infuriating . . . > > what *is* the scope of the passkey? > >I've tried setting it during stack initialization, even dumbing the >password down to "abc", and I'm still getting the "can't cut" error. > >Do I need to be setting it before every copy? > > >-- >Dr. Richard E. Hawkins, Esq. >(702) 508-8462 >_______________________________________________ >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 _______________________________________________ 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