Rev 3.0 Cloning problem

[Mark Schonewille]

Hi John,

The correct procedure is:

clone stack "resouce_template"
put it into myTempStackID
-- do other stuff here
set the name of myTempStackID to myStackName

You don't need the keyword "stack" before the variable containing the  
long ID of the new stack.

--
Best regards,

Mark Schonewille

Economy-x-Talk Consulting and Software Engineering
http://economy-x-talk.com
http://www.salery.biz
http://facebook.economy-x-talk.com

Benefit from our inexpensive hosting services. See http://economy-x-talk.com/server.html 
  for more info.

On 10 sep 2008, at 06:55, John Tregea wrote:

> Hi Fellow Rev'ers,
>
> I have been trying out Rev 3.0 across a number of iterations and  
> recently came across a problem (3.0gm Build 750).
>
> I have a piece of code that makes a clone of a stack, renames it and  
> then populates the new version of the stack with data from a  
> database. This has worked fine in 2.8, 2.9 and earlier iterations of  
> 3.0.
>
> The problem is that when the script gets to the clone command it  
> performs that line then just exits as if there is no more code. No  
> error is returned. Anyone seen this behaviour?
>
> The code looks like this.
>
> ifthereisnotastack tTheStack
> then
> clonestack"resource_template"
> send"choose browse tool"tomein1tick
> setthenameofstack it to tTheStack
> endif
>
> The variable tTheStack contains the name for the new stack. In debug  
> mode the variable is correctly populated, the stack IS cloned, then  
> the script just exits.
>
> Any help would be appreciated
>
> Regards
>
> John Tregea