Differentiating a substack from a mainstack

Mark Wieder mwieder at ahsoftware.net
Wed Nov 20 20:36:51 EST 2013


Wednesday, November 20, 2013, 5:29:54 PM, you wrote:

> I prowled around the IDE code for the File menu "New substack" item and
> here's what happens:

> *put* the short name of the topStack into tCurrentStack
> *if* the mainStack of stack tCurrentStack is not tCurrentStack *then* *put*
> the mainStack of stack tCurrentStack into tCurrentStack
> *send* "menuPick" && quote & "New Mainstack" & quote to button "file"
> *set* the mainStack of the topStack to tCurrentStack

> In other words, requesting a new substack results in a new mainstack being
> created then having it's mainstack set to the correct mainstack.

Yes, and that's what should happen, in spite of the asterisks.
Creating a stack is creating a stack.
The part that *might* be considered a bug is that saying

create stack "haha"

doesn't attach the new stack name until after the stack has been
created with a generic id name and the openstack handler has finished

-Mark Wieder
 ahsoftware at gmail.com

More information about the Use-livecode mailing list