What's a good strategy to make the grid more user friendly in the following situation:
The grid allows for multiple selection of rows and the user can delete selected rows.
Per default, if the selection includes the current row, and the data is reloaded, the current row is reset to the first row of the datasource.
This can be a bit confusing, especially if the user has set custom sorting differently from the orignial sort order of the dataset.
I would like to have the current row after the reload set to either the row immediately preceeding or following the previously selected (and now deleted) rows. That is, the grid should not, or only minimally scroll the contents.
A proposed solution should work regardless of the data that is loaded into the datasource. The code should not have to know the logical ID column of the rows.