Hi
I've read some articles in metacard lists about clone behaviour.
For myself I've now a strange error that I can't solve:
From a main stack A I call a substack B which has the handler
klonen. The handler klonen in substack B has the simple script:
on Klonen
put ZuKopieren _ Schuelername
Grüezi Andreas,
Hi
I've read some articles in metacard lists about clone behaviour.
For myself I've now a strange error that I can't solve:
From a main stack A I call a substack B which has the handler
klonen. The handler klonen in substack B has the simple script:
on Klonen
put ZuKopieren _
strange clone behaviour: bug?
From: andreas
Date: Tue, 13 Jul 2004 01:31:20 -0700
Hi
I've read some articles in metacard lists about clone behaviour.
For myself I've now a strange error that I can't solve:
From a main stack A I call a substack B which has
will experiment with this stack to produce the cloning error
and hope to post this soon.
Every hint is welcome!
Thanks
Andreas
Am 13.07.2004 um 13:17 Uhr schrieb Wouter:
strange clone behaviour: bug?
From: andreas
Date: Tue, 13 Jul 2004 01:31:20 -0700
Hi
I've read
Re: strange clone behaviour: bug?
From: andreas
Date: Tue, 13 Jul 2004 04:46:47 -0700
Hi Wouter
thanks for your hints - all Variables are globals and have
values.
I just isolated the code that clones the cards to 2 new stacks:
Stack A: sends the Klonen message
Andreas - I'm afraid this won't be of much help, but about a year ago, I reported a
problem with the clone function - we were executing it within a repeat loop and could
guarantee an eventual crash, although it was completely unpredictable as to _when_ it
would crash. It felt like a memory
Hi again,
A little addendum:
The other thing you have to check for before cloning a card is password
protection of the stack you are cloning from.
If protected and no passkey is entered there will be no cloning, only
error dialog.
Greetings,
Wouter
On 13 Jul 2004, at 18:00, [EMAIL PROTECTED] wrote:
Message: 7
Date: Tue, 13 Jul 2004 17:34:42 +0200
From: andreas [EMAIL PROTECTED]
Subject: Re: strange clone behaviour: bug?
To: How to use Revolution [EMAIL PROTECTED]
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain; charset=US-ASCII
On Jul 13, 2004, at 8:34 AM, andreas wrote:
you can't use clone to clone a card, if the card has grouped objects
on it
(for example, some grouped fields) and you use
a loop to make several clones.
If you haven't grouped objects on the card to clone, clone works
fine!
I'm not sure, if it is
Hi Mark
thanks for the link. This describes exactly what happens in this case.
I do have to clone about 10 cards per user. But Rev stops processing
after the first card. This card indeed has grouped objects! So it seems
that the cloning behaviour is a bug and isn't fixed in Rev 2.2.1 ?
Kind
On Jul 13, 2004, at 12:03 PM, andreas wrote:
Hi Mark
thanks for the link. This describes exactly what happens in this case.
I do have to clone about 10 cards per user. But Rev stops processing
after the first card. This card indeed has grouped objects! So it seems
that the cloning behaviour is a
I've queried the list in the past, as well, and got nowhere on this.
There's definitely a bug, but it is not predictable or consistent. I, too,
gave up using the clone function, and went to a sort of multiple blank
template approach. I guessed how many cards would be the most I'd ever
want in
I responded too soon. Should have checked the mail first--another 30 or
so messages. I'm glad to see it's being fixed. I'd queried bugzilla before I
posted, but used 'clone' rather than 'cloning' so didn't find anything. Don't
know whether I'll 'back up' in my project to use the workaround,
13 matches
Mail list logo
