Wohoo if that really works, then you just have fixed one of the biggest
issues I have had with the current component set, which I could not
figure out myself of what went wrong.
(in my debugging steps I lost the old datamodel at exactly that
situation, which was rendered
somewhere between encodebegin and encodechildren of the scroller and I
never could figure out why)
All we need now is a way to set the scroller position from outside, but
if your stuff really works, that one should be doable...
The scroller has all the needed hooks they just need to be exposed :-)
Werner
Mathias Broekelmann wrote:
Hi Werner,
yes it should fix this issue. You can use sortheader (immediate
attribute must be set to false for sortheader), inputfields, nested
uidatas and datascrollers with the patch for 305 and the new uidata
implementation.
Mathias
