You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by vov <vo...@mail.ru> on 2010/06/25 08:55:14 UTC

Re: inmethod custom PagingToolbar with dropdownchoice for setting rows not working correctly

Try to use:

yourDDC.add(new AjaxFormComponentUpdatingBehavior("onchange")
    {
      @Override
      protected void onUpdate(AjaxRequestTarget target)
      {
          target.addComponent(yourGridComponent); //like MyGrid.this
      }
    });
-- 
View this message in context: http://apache-wicket.1842946.n4.nabble.com/inmethod-custom-PagingToolbar-with-dropdownchoice-for-setting-rows-not-working-correctly-tp2266659p2268034.html
Sent from the Wicket - User mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org


Re: inmethod custom PagingToolbar with dropdownchoice for setting rows not working correctly

Posted by Sam Zilverberg <sa...@gmail.com>.
I've remove the filter-form and toolbar to see if they affect this
situation, sadly they dont.

When the rows-per-page DDC is outside the toolbar (and outside the grid
markup) choosing a value will correctly change the DDC's model object and
then the grid is rendered again using the correct DDC integer value.

When this DDC is inside the toolbar the grid is first rendered and only then
the DDC's model object is updated - causing a "delay" between the DDC's
model object and the grids rows per page value.

any ideas? or do I have to create a new grid instance as nino suggests?

Re: inmethod custom PagingToolbar with dropdownchoice for setting rows not working correctly

Posted by Sam Zilverberg <sa...@gmail.com>.
vov: adding this behavior doesn't solve the problem. with this behavior the
ddc never reaches the "getDataGrid().setRowsPerPage(newSelection);" line in
the code.