Re: copying from password protected substacks

Peter Haworth wrote: > I'm still not sure in my mind whether "encryption" is the same thing > as password protecting a stack. I've only ever used the latter. > Anybody know? AFAIK there is only one form of script encryption, set with the password property and unlocked during the session with t

Re: copying from password protected substacks

Right. I'm still not sure in my mind whether "encryption" is the same thing as password protecting a stack. I've only ever used the latter. Anybody know? Pete lcSQL Software Home of lcStackBrowser and SQLiteAdmin

Re: copying from password protected substacks

You can use this: function expandError pErr -- expands LC runtime error numbers, with explanatory text -- probably based on a handler from someone on the use-LC list, not sure who -- revised by Peter M. Brigham, pmb...@gmail.com — freeware -- requires sr() repeat for each li

Re: copying from password protected substacks

On 4/14/2015 8:26 PM, Peter Haworth wrote: Unless there's a bug somewhere in the decryption routines, it still feels like the passkey you are supplying is not the same one you specified in the standalone settings. That's what it sounds like to me too. I wonder how the standalone builder handle

Re: copying from password protected substacks

On 4/14/2015 8:17 PM, Dr. Hawkins wrote: However, where can I find the list of those codes, and what that error box means in general? User Sample Stacks (in the toolbar) -> LC Error Lookup or here: Or make your own, the locati

Re: copying from password protected substacks

The first item of each line refers to a line number in an error messages table. The table is in the cErrorsList custom property of card 1 of stack revErrorDisplay. Sounds like you set the encrypt with password field in the standalone settings. Make sure you do that for every stack you want to be

Re: copying from password protected substacks

On Tue, Apr 14, 2015 at 2:50 PM, Peter Haworth wrote: > Error 558 is "stack: invalid key". Not much help but perhaps the passkey > you're supplying isn't the correct one? Not likely I guess since it > apparently works in the IDE. > There is no password set in the IDE; it's all at compile time.

Re: copying from password protected substacks

Error 558 is "stack: invalid key". Not much help but perhaps the passkey you're supplying isn't the correct one? Not likely I guess since it apparently works in the IDE. Pete lcSQL Software Home of lcStackBrowser and SQLiteAdmin <

Re: copying from password protected substacks

On Tue, Apr 14, 2015 at 2:09 PM, Scott Rossi wrote: > Does it work for you in the IDE? > Yes. However, the password only gets set at compile time. > Also, you're not using the Community Edition are you? > *shudder*, no. Far too much work into this to risk GPL contamination/taiint of my cod

Re: copying from password protected substacks

Does it work for you in the IDE? Also, you're not using the Community Edition are you? You can't password protect with that version of LiveCode even though it shows the option in the Standalone Builder. Regards, Scott Rossi Creative Director Tactile Media, UX/UI Design On 4/14/15, 1:50 PM,

Re: copying from password protected substacks

On Tue, Apr 14, 2015 at 12:03 PM, Scott Rossi wrote: > 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. > but that doesn't see

Re: copying from password protected substacks

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

Re: copying from password protected substacks

On Sat, Apr 11, 2015 at 5:26 PM, Scott Rossi 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 initializ

Re: copying from password protected substacks

If you set the passkey of the protected stack (to the password) before copying, you should be able to copy what you want. Regards, Scott Rossi Creative Director Tactile Media, UX/UI Design On 4/11/15, 5:10 PM, "Dr. Hawkins" wrote: >Thanks. But this will make life *much* more difficult. Ca

Re: copying from password protected substacks

On Sat, Apr 11, 2015 at 3:59 PM, Mark Schonewille < m.schonewi...@economy-x-talk.com> wrote: > You can't copy controls from password protected stacks, because that would > allow you to paste controls on unprotected stacks and read the scripts. > Thanks. But this will make life *much* more diffic

Re: copying from password protected substacks

Hi Richard, You can't copy controls from password protected stacks, because that would allow you to paste controls on unprotected stacks and read the scripts. The solution is to create controls in an unprotected stack without scripts and set the parentScript of these controls to a button wit

Re: copying from password protected substacks

On Sat, Apr 11, 2015 at 3:52 PM, Dr. Hawkins wrote: > have found that when I try to copy a group from a stack that I clone > (turns out to be much faster to add objects to that group and delete the > group than to delete individual items), I get a "can't cut object. Also, all of the substacks