I think you could do something like this: clone this stack set the name of this stack to "my new stack" go stack "my previously only stack"
use lock screen and/or "go hidden" respectively "hide stack" to reduce screen flickering. On 23.05.2013, at 21:12, Peter Haworth wrote: > 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. > > > Pete > lcSQL Software <http://www.lcsql.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 an alternative Dictionary viewer: http://bjoernke.com/bvgdocu/ Chat with other RunRev developers: http://bjoernke.com/chatrev/ _______________________________________________ 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
