Continuing a script after cloning a stack

Peter Haworth pete at lcsql.com
Thu May 23 17:35:10 CDT 2013


Hi Jacque,
You've probably seen the follow up emails on this, but the noting after the
clone command executes.  I set a break point right at the clone command and
after stepping into the clone statement, the debugger did not advance to
the next statement and the script terminated.

Pete
lcSQL Software <http://www.lcsql.com>


On Thu, May 23, 2013 at 3:06 PM, J. Landman Gay <jacque at hyperactivesw.com>wrote:

> On 5/23/13 2:12 PM, 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
>>
>
> Actually, it isn't, the handler should continue to completion. I think
> something else must be interfering. You could try stepping through the
> script to find out where it's derailing.
>
> --
> Jacqueline Landman Gay         |     jacque at hyperactivesw.com
> HyperActive Software           |     http://www.hyperactivesw.com
>
>
> ______________________________**_________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/**mailman/listinfo/use-livecode<http://lists.runrev.com/mailman/listinfo/use-livecode>
>


More information about the use-livecode mailing list