jcompagner wrote:lwjwillemsen wrote:Case id 269546, Table view does not scroll into selectedIndex of form.foundset.
After upgrading to RC 1 (Version: 5.1.0 rc1 - build 953) we experience the problem as described fixed in RC1 !
Before RC 1 the scrolling was ok !
Regards,
what are you exactly doing?
Because what is fixed in RC1 that it stays exactly where it is.
So if you scroll to position X
go away from the tableview
then back
it is still in position X
But i guess you do something like:
onAction()
{
forms.xxx.foundset.setSelectedIndex(190)
forms.xxx.controller.show();
}
?
if you do this:
onAction()
{
forms.xxx.controller.show();
forms.xxx.foundset.setSelectedIndex(190)
}
then it works fine.
I will look if i can improve this. But the problem is that with the current multi select support constantly moving to the selection doesn't make much sense.
Also when you don't call setSelectedIndex() the form should be stable (no sudden scrolling because you moved for a moment to a different form and then back again)
What we do in our framework (Sanneke) is a toggleView which is a switch from a detailview form to a (different) tableview form.
What we do in the switch is a tabelviewform.foundset.loadRecords(detailviewform.foundset).
I can see in the tableviewform is that the selectedIndex is correct afterwards (ie after the loadRecords) but the selectedIndex is not in the UI.
In stead the first 20 or 30 records are in the view window.
I think the tableview view window update behavior (after selectedIndex change) has changed...
We dont use multi-select in our framework browser forms and viewer forms.
It seems that at the onShow event of the form the currently selectedIndex is not committed to the UI, ie not in the view port/window !
