A couple of weird things with cloned stacks

Doug Lerner doug at webcrossing.com
Fri Jan 9 10:41:04 EST 2004


(1) If I use the 

    set mainStack

command to cause cloned stacks to be a substack of the main stack it has the
inconvenient side-effect of storing all the created cloned substacks in the
main file when I save everything in the IDE.

It's probably better to duplicate main stack handlers in the clone itself
and leave it out of the mainstack.

(2)  If I use the

    set name

command to change the name of the newly cloned stack, the Application
Browser does not reflect the change. This is probably an Application Browser
bug.

doug



More information about the use-livecode mailing list