Page 2 of 2
Re: Problems compiling app with RunRev 4
Posted: Mon Jul 14, 2014 12:13 pm
by Mark
Yep, this problem still exists. Usually, I just click OK and ignore it.
Mark
Re: Problems compiling app with RunRev 4
Posted: Mon Jul 14, 2014 1:08 pm
by Mag
Thank you Mark
Re: Problems compiling app with RunRev 4
Posted: Mon Jul 14, 2014 1:17 pm
by Mag
Another message started to appear...
Re: Problems compiling app with RunRev 4
Posted: Mon Jul 14, 2014 1:23 pm
by Mark
Hi,
Are you using the commercial or the community version? In commercial versions, this can happen if the stack already has a password. Community versions should throw an execution error if a script tries to set a password. (Such an execution error looks different from this dialog window, but things are changing a lot lately, so maybe the dialog is now shown as a result of the execution error).
Kind regards,
Mark
Re: Problems compiling app with RunRev 4
Posted: Mon Jul 14, 2014 1:38 pm
by Mag
Thank you for the info. I'm using a commercial version.
So I have to just set the pw for the Mainstack? Do you know if this will protect also the substacks?
Re: Problems compiling app with RunRev 4
Posted: Mon Jul 14, 2014 1:58 pm
by Mark
Hi,
Probably, you tried to turn on password protection in the standalone settings for a stack that is protected by a password already. You have three options.
1) remove the password from that stack and just set all passwords for all stacks in the standalone settings
2) set the passwords of all stacks in the standalone settings, except for the password of the stack that is protected already
3) don't set any passwords in the standalone settings but use the message box (for example) to set the passwords of all mainstacks and substacks (except for the one that is already protected).
If you set the password of a mainstack, its substacks are still unprotected. You have to set a password for each mainstack and substack separately.
Kind regards,
Mark