I verified that if run from a script, the card will clone in the stack the script is running in. Otherwise it will clone in the stack the source card is in regardless of the topStack. Odd implementation if you ask me. I often need to create a new substack, then clone a card from another substack to save a lot of time copy pasting objects. Heretofore I've been unable to do that, but now I know, just place a button on card 1 of the new stack.
Bob S > On Aug 21, 2018, at 20:50 , Geoff Canyon via use-livecode > <use-livecode@lists.runrev.com> wrote: > > On Tue, Aug 21, 2018 at 7:50 AM Bob Sneidar via use-livecode < > use-livecode@lists.runrev.com> wrote: > >> SO THAT'S how you do it! And do you mean it clones to the topstack? >> Usually you would clone a card from the message box, and of course it >> cannot clone to that! >> >> Bob S >> > > I'm not 100% sure whether this a bug or not -- I filed Bug 21509 > <https://quality.livecode.com/show_bug.cgi?id=21509> to report it. Cloning > an object makes a duplicate in the same container as the original. Cloning > a card makes a duplicate in the stack where the script is running. I don't > know if the message box is somehow different than Navigator to prevent > this, or if there is code to prevent it happening in the message box like I > have now put in Navigator. We'll see what the response is. > > gc > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
