Continuing a script after cloning a stack
janschenkel at yahoo.com
Thu May 23 14:24:34 CDT 2013
My guess is something in its scripts (or some backscript) results in an 'exit to top'
Have you tried surrounding the clone command with a 'lock messages' / 'unlock messages' pair?
If you still need 'preOpenStack' and related messages to run afterwards, you'd have to 'send' them individually afterwards.
Quartam Reports & PDF Library for LiveCode
"As we grow older, we grow both wiser and more foolish at the same time." (La Rochefoucauld)
----- Original Message -----
From: Peter Haworth <pete at lcsql.com>
To: How to use LiveCode <use-livecode at lists.runrev.com>
Sent: Thursday, May 23, 2013 9:12 PM
Subject: Continuing a script after cloning a stack
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 <http://www.lcsql.com>
use-livecode mailing list
use-livecode at lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the use-livecode