Copy card question from 1 stack file to another

David Squance squance at elkvalley.net
Sun Jun 19 18:47:35 EDT 2005


Jim,
Perhaps it would work to copy one card, make sure the menu and field 
are grouped and the background behaviour is on and then clone the card 
with a repeat loop, either in the message box or with a button which 
could later be hidden or deleted, if this is a one-shot affair.  The 
button / msg box script could have a line to set the name of each card, 
if needed.
HTH,
Dave
On Jun 19, 2005, at 2:28 PM, Jim Bufalini wrote:

> Hi everyone,
>
> This has to be simple, but it has me stumped.
>
> I am running rev 2.51 on WinXP
>
> I am copying 20 cards from one stack file to a separate stack in 
> another
> file. The cards have two objects I am interested in, an option menu 
> button
> and a scrolling field. Selecting the option menu switches cards and 
> displays
> the text of the field on that card. This all works fine in the original
> stack.
>
> In the original stack, the option menu has the same ID across all 
> cards.
> (1784). The field also has the same ID across all cards.(1785). And 
> the two
> objects are grouped and set as background. The option menu button is 
> set to
> Display name.
>
> After I copy the 20 cards to anther stack in a separate file, 
> everything
> looks the same (grouping, settings, etc.), however each option menu and
> field has a unique ID in each card. So, when I select an option from 
> the
> option menu, it goes to the right card and displays the proper text in 
> the
> field, BUT, the display name of the option menu button is "floating" 
> and
> random from card to card.
>
> How do I copy the cards so that they are identical and work the same 
> in both
> stack files?
>
> Jim
>
>
>
>
>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your 
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution
>



More information about the use-livecode mailing list