Martin Marinschek wrote:
Sorry,
don't know so many details about the data-scroller, but I think Thomas
said that this is a problem still to be overcome.
Maybe you would want to work on that and provide a patch?
I think I found the affected part of the datascroller.
The think is, that the datascroller saves the current scroller
position over its id in the request parameter map.
But once the event is not triggered by the scroller,
the position is not saved over its name in the global request parameter
map and basically the scrollers position setting routines in the
renderer are not triggered that way.
I will try to fix that in the weekend against the 1.0.9 sources.
I am not entirely sure about the best way to fix that.
But my best guess is the introduction of a saveState attribute, which
restores last position state from the session, if set to true, once the
renderer of the scroller runs against an empty attribute.
That way you can turn on the savestate restoration selectively upon a
given state of a backend bean.
Because often you dont really want to have the state safed.
I would rather not having to doctor around at the original sources yet
or having to implement yet another component, since my schedule still is
too tight, but oh well... That´s life.
