Re: Remove the password protection of a stack Application browser
From: Scott Rossi sc...@tactilemedia.com Message box: set passKey of stack xyz to abc To remove a password after setting the passKey: set password of stack xyz to empty passKey will do the trick. Thanks Scott! From: Shari sh...@gypsyware.com It is indeed called the Control Browser and you can access it from the Tools menu. It is very different from the Rev Application Browser. (I say Rev because I've not downloaded the LiveCode version yet so I don't know if it changed from the Rev version.) Ok, thanks Shari! From: J. Landman Gay jac...@hyperactivesw.com MC is more like a command line app, with only a minimal GUI. There are a few more improvements in it now than originally but it still is missing many of the interface items that LiveCode provides. The object inspectors contain only the basic, most-used items, and everything else you must set from the message box. That applies to passwords too. In fact, if you don't know a property exists you are likely to miss it entirely because the IDE has no reference to it. It does force you to learn the whole language though. :) I love command line apps a lot... Or maybe not ;) Thanks Jacque! I should find my way in the dark. Jacque, Shari and Scott, thanks for your replies to my newbie questions. Best regards, TheSlug ___ metacard mailing list metacard@lists.runrev.com http://lists.runrev.com/mailman/listinfo/metacard
Re: Remove the password protection of a stack Application browser
* Message box: set passKey of stack xyz to abc To remove a password after setting the passKey: set password of stack xyz to empty * One wonders what the point of password protection is then (at least vis-a-vis stacks). ___ metacard mailing list metacard@lists.runrev.com http://lists.runrev.com/mailman/listinfo/metacard
Re: Remove the password protection of a stack Application
1) How removing the password protection of a stack in the MC IDE. In the LC IDE the IDE asks me for the password when I'm trying to open a script in the stack. In the MC IDE, I'm informed that the stack is password protected but not asking a password Hi zryip The MC IDE lost the ability to set/remove a password became lost after v4.0 when the encryption in the engine changed. I think we are still waiting for Edit menu Stack Properties Password/Passkey button to be updated. Klaus? Personally I never use the LC IDE until I need to build a standAlone or protect a stack. Passwording is a pain, though, because I have to open a protected in LC, try to edit a script, enter the password to temporarily unlock it, use the message box to set the password of this stack to empty, save the stack, then return to MC to continue. Fortunately I do not have to do this frequently. Fortunately when building a standAlone, setting the password at build time does not affect the source stack itself. Hugh Senior FLCo ___ metacard mailing list metacard@lists.runrev.com http://lists.runrev.com/mailman/listinfo/metacard
Re: Remove the password protection of a stack Application browser
Recently, Richmond wrote: Message box: set passKey of stack xyz to abc To remove a password after setting the passKey: set password of stack xyz to empty One wonders what the point of password protection is then (at least vis-a-vis stacks). I don't know what the actual state of password protection is in MC, but in general you cannot change/undo a stack's password without knowing that password. The passkey string above is the same as the stack's password string; you are prevented from setting the password property directly, without first setting the passkey to the stack's password. Plus, setting the passkey property is temporary, working only for the current session until the stack is removed from memory. The next time you open the stack, the password is enabled and scripts are protected. It may sound a bit roundabout, but I'm sure it's no different that what LiveCode uses in the IDE. Regards, Scott Rossi Creative Director Tactile Media, UX Design ___ metacard mailing list metacard@lists.runrev.com http://lists.runrev.com/mailman/listinfo/metacard
Re: Remove the password protection of a stack Application
On 12/16/10 1:01 PM, FlexibleLearning wrote: The MC IDE lost the ability to set/remove a password became lost after v4.0 when the encryption in the engine changed. It works if you use the message box though. I think we are still waiting for Edit menu Stack Properties Password/Passkey button to be updated. Klaus? Oh -- I see what you mean now. You know, I never noticed that was in there! I can also see the problem, it's the same one Richard reported on the LiveCode list. The passkey and password won't match any more, even if they are the same. I've forgotten the workaround but Richard would know. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com ___ metacard mailing list metacard@lists.runrev.com http://lists.runrev.com/mailman/listinfo/metacard
Re: Remove the password protection of a stack Application browser
On 12/16/10 12:45 PM, Richmond wrote: * Message box: set passKey of stack xyz to abc To remove a password after setting the passKey: set password of stack xyz to empty * One wonders what the point of password protection is then (at least vis-a-vis stacks). Well, you do have to know what the password is to unlock the stack. The point being that you, as a developer, can get in but others can't. Another big advantage of setting a password is that the stack content is encrypted and can't be read in a text editor, so the scripts are protected from snoopers. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com ___ metacard mailing list metacard@lists.runrev.com http://lists.runrev.com/mailman/listinfo/metacard
Re: Remove the password protection of a stack Application browser
On 16.12.2010 at 15:08 Uhr -0600 J. Landman Gay apparently wrote: Well, you do have to know what the password is to unlock the stack. The point being that you, as a developer, can get in but others can't. With the exception of http://quality.runrev.com/qacenter/show_bug.cgi?id=546 However, there was some changes somewhere in engine 4 that changed some of the behavior. I recall a discussion on the rev-use list but forget the details. Robert ___ metacard mailing list metacard@lists.runrev.com http://lists.runrev.com/mailman/listinfo/metacard
