LiveCode Forums.

Hello,

I'm cloning a stack, since I need to create an exact copy of a substack. Now I found to big problems:

1) New stack created (cloned) is a main stack.
2) New stack created (cloned) has the same ID of the original substack!

It means I cannot assign the new stack as a substack (change "mainStack" property).

Please help me since I cannot continue to work, and this is a key-feature for me!

Thank you for your help.

ale870,
although I dont quite understand what you are doing, you can change the id of a stack, maybe that helps
regards
Bernd

Thank you!
I tried reassign the code but I could not do that.
Now I tried again and I found that I assigned low numbers (RunRev requires an ID bigger than the current id number).
Now as workaround I'm using altid.

Thank you for your tip!

Thank you!
I tried reassign the code but I could not do that.
Now I tried again and I found that I assigned low numbers (RunRev requires an ID bigger than the current id number).
Now as workaround I'm using altid.

Thank you for your tip!

Thank you!
I tried reassign the code but I could not do that.
Now I tried again and I found that I assigned low numbers (RunRev requires an ID bigger than the current id number).
Now as workaround I'm using altid.

But the main problem is not solved (cloning stack RunRev does not generate a correct ID).

Thank you for your tip!

I also don't understand what you're trying to do or why you have a problem.

clone stack "mySubStack"
set the name of it to "myNewSubStack"
set the mainstack of stack "myNewSubStack" to "myMainStack"

Does that not do what you want? Why do you care about the id of the substack?

Because it seems RunRev 4.5-dp3 create a new stack with the same id of the old one, and when I refer to it, RunRev cannot manage it since the IDs are the same

You shouldn't be referring to stacks by id. Ever. A new stack will *always* have an id of 1002. The code I posted works fine. Rev has no problems accessing substacks, even with the same id. The problem is with your code.

My code is ok, since I changed working mode from stack name to stack altId, and now everything works.
I think there could be some problems in the new beta release 4.5 dp-3.

Thank you.

Stack name should still work fine.

But yes, there are major problems with 4.5dp3. As there were with dp2. They're both beta - if you find problems, you should log them in the QCC.