I checked that early on and again today, cantEdit is false. The style was reported as toplevel but I set it again anyway in the message box. The command that opens the stack is a plain "go stack", the same as all the others in the suite that open normally. GRevDevolppment is true.

The only difference between this stack and hundreds of others is the name, as far as I can see.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On October 8, 2018 5:35:27 PM Richard Gaskin via use-livecode <use-livecode@lists.runrev.com> wrote:

J. Landman Gay wrote:

> I was able to look at this again today. The style of the stack is
> toplevel, it is visible and frontmost, but the mode is 2. This is true
> whether gRevDevelopment is true or false. Show IDE stacks in Lists is
> turned on.
>
> It's stuck that way. LC 9.0.1.

The style is the persistent property which governs mode when opened
using "open" or "go"; the mode is the current actual mode, which can
differ from the style if opened using a mode name as a command (e,g,
"palette <stackname>").

When the mode is 2 that usually means the cantEdit has been set.  This
may have been set somewhere in the IDE, thinking it's an IDE stack.

What happens if you set the cantEdit of the stack to false?

--
 Richard Gaskin
 Fourth World Systems
 Software Design and Development for the Desktop, Mobile, and the Web
 ____________________________________________________________________
 ambassa...@fourthworld.com                http://www.FourthWorld.com

_______________________________________________
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

Reply via email to