copy group to new stack

[André.Bisseret]

Hi Henk,
I looked a bit further at your stack (I did not look at the scripts  
before). I think I understand what you want to do.

I made some trials with one new stack "'stackOne" with one group on  
it : a button "label" and a fld with a phrase in it (named  
groupToBeCopied)
I put in the script of the field the following simple handler :
on mouseUp
create stack "stackTwo"
go to stack "stackTwo" -- not sure that'is necessary
create cd
copy group "groupToBeCopied" of stack "stackOne" to cd 1 of stack  
"stackTwo"
end mouseUp

Seems that it works, but ONLY if  the" share Text"  property of the  
field is set to true

I don't exactly understand why ?? but I can go further right now
Could be a way toward a solution ?

Best regards from Grenoble
André

Le 18 déc. 06 à 19:38, Henk van der Velden a écrit :

> I did some further testing to find out what is the simplest way to  
> reproduce this behaviour (I sort of consider it to be a bug).
> Essentially it comes down to this:
>
> 1. there are two stacks, A and B
> 2. in stack A a command is issued, consisting of:
> 2a: create a new card in stack B
> 2b: copy an editable text field from stack A to stack B
>
> It turns out that the text of the editable text field is not copied  
> to stack B, only the (empty) field.
> If you skip step 2a, both the editable field and its content are  
> copied to stack B.
>
> Any opinions on this?
>
> Henk
>
>> Hi André,
>>
>> The stack is a stripped down version of a print function.
>>
>> I want to print a number of groups from a stack to different pages.
>> In the stack all these groups are on one and the same card.
>> So I create an invisible stack, create the number of cards that is
>> needed and copy the groups to these cards. Now it turns out that the
>> contents of certain fields are not copied.
>>
>> It took me some time to find out why that happened.
>> I think I have pinpointed the problem to this one factor: if I create
>> a stack, then create new cards in that stack, and then copy fields to
>> it, the text is not copied (at least the text of editable fields). If
>> I create a stack, but don't create new cards in that stack, than the
>> copying works fine.
>>
>> Henk
>>
>> > Hi Henk,
>> > Not sure to understand precisely your problem ; seems to be that  
>> you
>> > should group  your fld "fld_conclusion"  and set it to "behave  
>> like a
>> > background". So your fid would be there on the second card.
>> >
>> > just one first idea
>> >
>> > Best regards from Grenoble
>> > André
>> >
>> > Le 18 déc. 06 à 16:09, Henk van der Velden a écrit :
>> >
>> > > Good day all,
>> > >
>> > > Here is a link to a stack that creates a new stack, creates an
>> > > extra card in that stack and then copies a group of text fields
>> > > into that new card.
>> > > Something strange happens: the contents of an editable field are
>> > > not copied.
>> > >
>> > > As you can see in this stack, all works OK if you don't create an
>> > > extra card. But as soon as you create one, the copying fails.
>> > > Can anyone tell me what's going on here?
>> > >
>> > > The stack can be downloaded here:
>> > http://www.iglow-media.nl/xchange/CopyToNewStack.zip
>> > >
>> >
>>
> _______________________________________________
> 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
>
>