That is a known issue, unfortunately you will need to create your own version of a submittingpagingnavigator. The api for those classes is however not very extendable friendly so you probably end up copy-pasting large portions of code. I believe Martijn is planning on refactoring that component, just not for wicket 1.3.x.
As an alternative you might be able to use ajaxcheckboxes? Maurice On Tue, Mar 18, 2008 at 12:30 PM, Trevor Campbell <[EMAIL PROTECTED]> wrote: > I have a form containing a GridView with a PagingNavigator. > Within each cell I have an image and a CheckBox. When a user submits > the form I collect all the image refs from the selected cells and > process them. > > My problem is I would like to do this across multiple pages. So the user > scenario is: > A user goes through the pages using the navigator and selects, using the > checkboxes, what images they like and then presses a select button. > > Unfortunately the selections are not preserved when I use a > PagingNavigator on the form. A paging navigator renders links rather > than a submit, so any selections are lost. > > Any ideas how to get around this?? > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
