Continuing a script after cloning a stack

Peter Haworth pete at
Thu May 23 15:12:00 EDT 2013

I have a script that clones a substack, followed by some other commands to
rename the cloned substack and set it's mainstack.  As soon as the clone
command is issued, control passes to the cloned stack and the rest of my
script is ignored.

That's pretty much expected behavior but I'm wondering if there are any
tricks that would allow my script to continue processing or perhaps some
other method of duplicating a stack.  I tried copying the stack to the
clipboard followed by a paste but control passed to the new
stack immediately after the paste.

lcSQL Software <>

More information about the Use-livecode mailing list