Return-Path: Delivered-To: apmail-cocoon-users-archive@www.apache.org Received: (qmail 81292 invoked from network); 30 Sep 2004 00:02:39 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 30 Sep 2004 00:02:39 -0000 Received: (qmail 28197 invoked by uid 500); 30 Sep 2004 00:02:24 -0000 Delivered-To: apmail-cocoon-users-archive@cocoon.apache.org Received: (qmail 28156 invoked by uid 500); 30 Sep 2004 00:02:23 -0000 Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: users@cocoon.apache.org Delivered-To: mailing list users@cocoon.apache.org Received: (qmail 28132 invoked by uid 99); 30 Sep 2004 00:02:23 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from [61.88.150.36] (HELO domino.travelthere.com) (61.88.150.36) by apache.org (qpsmtpd/0.28) with ESMTP; Wed, 29 Sep 2004 17:02:20 -0700 Received: from [10.55.4.5] ([10.55.4.5]) by domino.travelthere.com (Lotus Domino Release 6.5.1) with ESMTP id 2004093009311891-1285 ; Thu, 30 Sep 2004 09:31:18 +1000 Message-ID: <415B4592.5040001@contal.net.au> Date: Thu, 30 Sep 2004 09:30:26 +1000 From: Adam Walsh User-Agent: Mozilla Thunderbird 0.7.2 (Windows/20040707) X-Accept-Language: en, fr-fr, en-us MIME-Version: 1.0 To: users@cocoon.apache.org Subject: Re: continuation woes References: In-Reply-To: X-MIMETrack: Itemize by SMTP Server on domino/travelthere(Release 6.5.1|January 21, 2004) at 30/09/2004 09:31:18 AM, Serialize by Router on domino/travelthere(Release 6.5.1|January 21, 2004) at 30/09/2004 10:03:10 AM, Serialize complete at 30/09/2004 10:03:10 AM Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii; format=flowed X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Hi Jorg, That scenario makes perfect sense. In step 1, you're actually updating the model of your form by removing the element. Step 2 you're jumping back and seeing an old view of your form model that is no longer valid. In step 4 you're effectively just refreshing your view on the model, so it won't show the element that you removed previously. It's not actually being removed again, it's presenting the updated repeater widget with the element missing that you removed in step 1. An important thing to remember is that flow doesn't remember the history of your variables (including whatever you bind your CForm to) at each continuation. So if you update your repeater 7 times, then hit back 7 times and then refresh the page, the state of your repeater widget will be as it was at the end of your 7 updates. Does that make sense? HTH, Adam Jorg Heymans wrote: > Hi, > > Scenario > > 1) select an element from repeater, press "remove selected elements" > 2) press back in the browser, the removed element appears again with > its checkbox checked > 3) uncheck that checkbox > 4) press "remove selected elements" (should do nothing) > 5) the element is removed again ! > > After 2), which continuation becomes active again? Is it the one that > was created after the remove button was pressed or the one that was > created before the remove button was pressed ? > > > Regards > Jorg > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org > For additional commands, e-mail: users-help@cocoon.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org For additional commands, e-mail: users-help@cocoon.apache.org