1. clone the stack (via a script in a button etc.)
2. immediately rename that stack (then another copy can't be the same name)
Now you have your main stack and another main stack. If you want the cloned stack to be apart of the main stack then do 3. if not you can close it or whatever you want or skip 3. and move on to 4. etc.
3. set the mainStack of "cloned stack" to "MyMainStack"
This way there is no need to close the cloned stack and IDs are resolved via the IDE. This of course works only if you want the cloned stack to be a substack of the main stack.
If not it should not matter because they are at this time completely different stacks so the IDs should not matter.
I go the extra step and: 4. set the size of the cloned stack (now a substack) 5. set the position of the cloned stack 6. set the title of the cloned stack 7. set the name of the cloned stack 8. set any other things that need done.
I do all of this before cloning another stack or substack and have no problems.
Tom
On Jan 9, 2004, at 10:06 AM, Doug Lerner wrote:
So...
Are you saying something like:
1. clone a stack 2. set the name of the stack to something unique 3. close the stack again and 4. set the name of the stack to something unique etc
rather than leaving them all with the name "Copy of stack thisStack"?
What about the fact that the ids are the same?
doug
On 1/9/04 11:30 PM, "Thomas J McGrath III" <[EMAIL PROTECTED]> wrote:
Doug,
From what I understand, this is not a good thing to do. FWIW you can
clone a stack and then change the name and then set it to the mainStack
"Whatever" and for that matter change it's size location and add
scripts to it all via scripts.
In fact my experience shows that this is preferred over the single line
message box method. I experienced very weird behavior so switched to
putting a script in my main stack temporarily to build clones and
change them in one step.
The big thing to watch out for is in the naming of the clones!! Do not
use just numbers!! It will crash the stack and mess things up. I used a
series of numbers to build substacks like "13i" , "13ii" etc based upon
certain things and then one clone was "17" with on i in it and wham
there came the crash and a substack that could not be deleted and
caused the stack to not work. Luckily this list helped me and I had a
back up.
TOm
On Jan 9, 2004, at 7:01 AM, Doug Lerner wrote:
If I do a
clone stack "myStack"
Then a clone of the stack appears with the name "Copy of myStack".
If I then clone again I get *another* stack with the same name - "Copy
of
myStack" and same ID.
How do I distinguish between them?
Can I decide the cloned stack name myself?
doug
_______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Macintosh PowerBook G-4 OSX 10.3.1, OS 9.2.2, 1.25 GHz, 512MB RAM, Rev 2.1.2
Advanced Media Group Thomas J McGrath III • 2003 • [EMAIL PROTECTED] 220 Drake Road, Bethel Park, PA 15102
_______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Macintosh PowerBook G-4 OSX 10.3.1, OS 9.2.2, 1.25 GHz, 512MB RAM, Rev 2.1.2
Advanced Media Group Thomas J McGrath III • 2003 • [EMAIL PROTECTED] 220 Drake Road, Bethel Park, PA 15102
_______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
