Re: strange clone behaviour: bug?
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 _ Schuelername into NeuerName go card ZuKopieren clone card ZuKopieren set the name of it to NeuerName end Klonen On the line clone card ZuKopieren the script exits without an error message! Did you check the result immediately after this line? Might give some hints why the script stops here... This script boiled down from a far more complicated script, which showed the same error. This happens with the newest Rev built in MacOSX. Because my project relies heavily on the clone function help is very welcome! Sorry, no other idea right now... Andreas Stämpfli Regards Klaus Major [EMAIL PROTECTED] http://www.major-k.de ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Re: strange clone behaviour: bug?
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 the handler klonen. The handler klonen in substack B has the simple script: on Klonen put ZuKopieren _ Schuelername into NeuerName go card ZuKopieren clone card ZuKopieren set the name of it to NeuerName end Klonen If we must relay on the script above then: ZuKopieren is not initialized (name), it will be an empty var. There will be no error dialog, it will only return no such card and going nowhere. Cloning a card will cause an error dialog, so you exit on this line. Next if Schuelername is not initialized, you wil only be adding an underscore to the name On the line clone card ZuKopieren the script exits without an error message! so change your handler into something like this: on Klonen ZuKopieren put some name into Schuelername put ZuKopieren _ Schuelername into NeuerName go card ZuKopieren clone card ZuKopieren set the name of it to NeuerName end Klonen This script boiled down from a far more complicated script, which showed the same error. This happens with the newest Rev built in MacOSX. Because my project relies heavily on the clone function help is very welcome! Andreas Stmpfli HTH Greetings, WA ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Re: strange clone behaviour: bug?
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 to substack B: send Klone to stack substackB strange: in the new created stacks this works fine! No errors with cloning. I 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 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 into NeuerName go card ZuKopieren clone card ZuKopieren set the name of it to NeuerName end Klonen If we must relay on the script above then: ZuKopieren is not initialized (name), it will be an empty var. There will be no error dialog, it will only return no such card and going nowhere. Cloning a card will cause an error dialog, so you exit on this line. Next if Schuelername is not initialized, you wil only be adding an underscore to the name On the line clone card ZuKopieren the script exits without an error message! so change your handler into something like this: on Klonen ZuKopieren put some name into Schuelername put ZuKopieren _ Schuelername into NeuerName go card ZuKopieren clone card ZuKopieren set the name of it to NeuerName end Klonen This script boiled down from a far more complicated script, which showed the same error. This happens with the newest Rev built in MacOSX. Because my project relies heavily on the clone function help is very welcome! Andreas Stmpfli HTH Greetings, WA ___ 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
Re: strange clone behaviour: bug?
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 to substack B: send Klone to stack substackB strange: in the new created stacks this works fine! No errors with cloning. I will experiment with this stack to produce the cloning error and hope to post this soon. Every hint is welcome! Hi Andreas, Ok, it were globals (difficult to tell from your original post :-) If you want to clone a card from stack A into stack B and stack B is the default stack you can use: clone card ZuKopieren of stack stackname the card from stack A will be cloned into stack B after the card where klonen was ordered. !!! very important: first you have to check the cantmodify of stack stackname. - If set, you first have to set it to false, clone the card and reset the cantmodify. Or you get an error message telling you the stack is locked. - If not set, you can clone straight away. so your script could become something like: global ZuKopieren, Schuelername,gStack2Copy2, gStack2CopyFrom on Klonen put ZuKopieren _ Schuelername into NeuerName put the cantmodify of stack gStack2CopyFrom into tCantModif set the cantmodify of stack gStack2CopyFrom to false --go card ZuKopieren set the default stack to gStack2Copy2 clone card ZuKopieren of stack gStack2CopyFrom set the cantmodify of stack gStack2CopyFrom to tCantModif set the name of it to NeuerName end Klonen HTH Greetings, Wouter ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Re: strange clone behaviour: bug?
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 disconnect of some sort, whether it was a lost pointer or something like that, I can't say. We finally abandandoned this use of the clone and instead went to using copy to functionality. I don't recall seeing a response to the clone problem, but it was pre-bugzilla (and I'd since lost interest in the problem). Sorry. Ray On Tuesday, July 13, 2004, at 04:31AM, andreas [EMAIL PROTECTED] wrote: 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 into NeuerName go card ZuKopieren clone card ZuKopieren set the name of it to NeuerName end Klonen On the line clone card ZuKopieren the script exits without an error message! This script boiled down from a far more complicated script, which showed the same error. This happens with the newest Rev built in MacOSX. Because my project relies heavily on the clone function help is very welcome! Andreas Stämpfli ___ 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
Re: strange clone behaviour: bug?
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 ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Re: strange clone behaviour: bug?
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; format=flowed Hi Walter thanks for your assistance! I can reproduce the error, this seems like a bug. 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! After how many cards do you crash? This is indeed very weird, because I seem not to have any trouble cloning cards with groups of fields and buttons on them. For example cloning 100 cards of the revDocsLanguageReference and 150 cards of the metatalk reference stack to another stack poses no problem whatsoever. Only in rev it takes much longer (forever :-) than in metacard. If you have time, try your handler on the revDocsLanguageReference stack and see if it crashes. If it crashes on 100 cards there could be some offending code or I didn't clone enough cards to reach the bug :^) Greetings, Wouter ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Re: strange clone behaviour: bug?
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 possible, to use the copy card approach. But it seems not either. A bug? Hi Andreas, Take a look at bug: 1273 http://www.runrev.com/revolution/developers/bugdatabase/show_bug.cgi? id=1273 This may relate to you. They just reported that the bug has been fixed. -- Best regards, Mark Talluto http://www.canelasoftware.com ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Re: strange clone behaviour: bug?
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 regards Andreas Staempfli Am 13.07.2004 um 20:07 Uhr schrieb Mark Talluto: 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 possible, to use the copy card approach. But it seems not either. A bug? Hi Andreas, Take a look at bug: 1273 http://www.runrev.com/revolution/developers/bugdatabase/show_bug.cgi? id=1273 This may relate to you. They just reported that the bug has been fixed. -- Best regards, Mark Talluto http://www.canelasoftware.com ___ 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
Re: strange clone behaviour: bug?
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 bug and isn't fixed in Rev 2.2.1 ? Hi Andreas, That is correct. It will be fixed for the next release. There is a workaround though. Set the lockMessages to true before you do your cloning. You can unlock when that handler finishes. That should do the trick for now. -- Best regards, Mark Talluto 28612 Avalon Ave Moreno Valley, CA 92555 tel: (310) 483-9919 fax: (909) 924-6240 http://www.canelasoftware.com ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Re: strange clone behaviour: bug?
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 the stacks, and marked the active ones. Then, when I would otherwise clone a card, I just mark one of the spares, enter the data and proceed from there. It's a bit more cumbersome, and causes some stack bloat, but it's reliable (so far). Dave 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 disconnect of some sort, whether it was a lost pointer or something like that, I can't say. We finally abandandoned this use of the clone and instead went to using copy to functionality. I don't recall seeing a response to the clone problem, but it was pre-bugzilla (and I'd since lost interest in the problem). Sorry. Ray On Tuesday, July 13, 2004, at 04:31AM, andreas [EMAIL PROTECTED] wrote: 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 into NeuerName go card ZuKopieren clone card ZuKopieren set the name of it to NeuerName end Klonen On the line clone card ZuKopieren the script exits without an error message! This script boiled down from a far more complicated script, which showed the same error. This happens with the newest Rev built in MacOSX. Because my project relies heavily on the clone function help is very welcome! Andreas Stämpfli ___ 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 ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Re: strange clone behaviour: bug?
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, but it's nice to have the option. Dave 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 the stacks, and marked the active ones. Then, when I would otherwise clone a card, I just mark one of the spares, enter the data and proceed from there. It's a bit more cumbersome, and causes some stack bloat, but it's reliable (so far). Dave 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 disconnect of some sort, whether it was a lost pointer or something like that, I can't say. We finally abandandoned this use of the clone and instead went to using copy to functionality. I don't recall seeing a response to the clone problem, but it was pre-bugzilla (and I'd since lost interest in the problem). Sorry. Ray On Tuesday, July 13, 2004, at 04:31AM, andreas [EMAIL PROTECTED] wrote: 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 into NeuerName go card ZuKopieren clone card ZuKopieren set the name of it to NeuerName end Klonen On the line clone card ZuKopieren the script exits without an error message! This script boiled down from a far more complicated script, which showed the same error. This happens with the newest Rev built in MacOSX. Because my project relies heavily on the clone function help is very welcome! Andreas Stämpfli ___ 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 ___ 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
