Since nobody answers I try to reformulate the question differently.
The datascroller basically uses the pageIndexVar to set the position.
If I scroll everything is fine.
But as soon as I do a form submit outside of the datascroller,
the pageIndex var is reset to the first position.
My question is, is there a way to prevent this reset of the scroller
page index? x:saveState does not seem to work in this case.
Werner
Werner Punz wrote:
Hi, I have a problem regarding the x:dataScroller component, which I try
to figure out.
I have a problem of having a table with a datascroller and a backend model.
The table is filled correctly, the scroller works as supposed.
But I now have an action link in the table, which does some actions (in
my case marking a dataset for operation)
This also works as long as I am on page 1 of the scroller.
But strange things happen as soon as I try to do it at a subsequent page.
The operation is triggered and works according to the code perfectly,
and as soon as I return, the scroller basically resets to page 1.
I am not quite sure how to resolve this, a quick look at the code
showed me that I could trigger the same links as the scroller does, or
misuse the binding var.
But is there a standardized easy way to do this.
x:saveState on the binding var, does not really seem to work in thise case.
