Re: Continuing a script after cloning a stack

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 Softw

Re: Continuing a script after cloning a stack

On 5/23/13 5:00 PM, Richard Gaskin wrote: Such things are at best confusing, and at worst drive up the cost of developing with LiveCode because you have to build a standalone just to test Or suspend the environment. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive

Re: Continuing a script after cloning a stack

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 m

Re: Continuing a script after cloning a stack

Peter Haworth wrote: Hi Richard and Jan Locking messages fixed the problem. This is a general purpose routine so I have to deal with any preOpenxxx and open handlers that might be in the stack. I think I will have to add code to close and re-open the stack after the renaming and setting of

Re: Continuing a script after cloning a stack

Hi Richard and Jan Locking messages fixed the problem. This is a general purpose routine so I have to deal with any preOpenxxx and open handlers that might be in the stack. I think I will have to add code to close and re-open the stack after the renaming and setting of the main stack once I h

Re: Continuing a script after cloning a stack

Hi Bjornke, Problem is, it never reaches the "set the name" command because foucs has shifted to the cloned stack Pete lcSQL Software On Thu, May 23, 2013 at 12:27 PM, Björnke von Gierke wrote: > I think you could do something like this: > clone this stack > set the name

Re: Continuing a script after cloning a stack

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. We could expect focus to change to

Re: Continuing a script after cloning a stack

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 t

Re: Continuing a script after cloning a stack

: Peter Haworth To: How to use LiveCode Cc: 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

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