Hi Bob,

thanks for the answer.
I totally forgot about the POST and GET difference *shame on me* Now it makes perfect sense to me, why the table "forgets" the CheckBox status while paging. It's only about this one table in my application. So I won't change the framework, since for the rest of the application the Click-Framework is just perfect :) I'll find a solution, that will work for me. At worst I process the data pagewise ;)

Thanks again.
Best regards
Anja


Am 08.11.2011 08:06, schrieb Bob Schellink:
Hi Anja,

When the user fills in the fields they need to post the data to the
server, normally  by clicking the submit button. It sounds what you
are after is to post the field data when the user clicks on the paging
link? Links always perform a GET request, Click doesn't change this
behavior. You could use JavaScript to submit the data but this is
approaching the domain of JavaScript heavy applications. If your
requirement is to build a highly interactive and JavaScript heavy
application you might want to look at other technologies such as GWT,
Vaadin or ZK.

Hope this helps.

regards

Bob

On 2011/11/07 10:52 AM, Anja Bethge wrote:
Hello,

I have a FormTable with a FieldColumn containing a Checkbox and an 
InlinePaginator. I want to be able to select rows via the CheckBox on all pages 
of the table and then click a Submit-Button to process the selected data.

Now I have the following problem:
When I click the CheckBox in a row and thus change the status from unchecked to checked 
or vice verca and then switch to another page of the table, the table "forgets" 
the changed CheckBox status. When I return to the previous page, the CheckBox status will 
be the same as it was at the first initialization of the page.
You can check up this behavior at the Click Examples site (FormTable): 
http://click.avoka.com/click-examples/table/form-table.htm

This behavior is quite logic, since a new request for the corresponding page is 
created, whenever the Paginator is used. When the table is used only to display 
the data, this is fine enough. But when a FormTable is used to edit the 
displayed data I assumed that switching to another page would cause the table 
to transfer the changed data from the table to the provided data model, like 
its seem to do when the getRowList() method is called. But it doesn't.

Does anybody knows a quick workaround? There seems to be no way to add a 
listener to the table page links, so that I can force the table to update the 
data model, without overwriting the TablePaginator.

Best regards
Anja


Reply via email to