We have some scenarios in which we need to have continuous virtualization, which works well.
However, when the user edits a cell and then leaves it the style of the row is not maintained as it is in non-continuous mode, so it appears to the user as though they no longer have an active row.
In addition, if we call endEdit directly on the grid, the same issue occurs.
Unfortunately, I am afraid this is going to be a pretty big issues for our customers, since the primary reason that we are switching to igGrid is to support large datasets and when working in a large data set, it's going to be difficult if the user keeps losing their visual cue on which item they are working on.
Hello Karl,
I have created sample based on your description. With this sample I was able to reproduce the issue – when one of the cells is edited and then leaved the selection disappears.
I have created a support case in our system for this issue with number – CAS-110996-Z0H2K3.
You will get further details regarding this issue through the case.
Thank you.
Sorry, I should have provided additional information: we are using cell edit mode with automatic commitment. We are using the standard metro theme.
The specific scenario is this:
The user selects a row and the row is highlighted.
The user clicks in a cell and changes the value. The rest of the row is still highlighted.
The user tabs to the next cell. The grid is updated, but the rest of the row loses the highlighting.
The problem is that when an event occurs that takes the current cell out of edit mode, it is impossible to tell which row is being operated on.
In our scenario, when a user selects an item from a combo, we force editing to end, but this problem also occurs if the user clicks on a non-editable cell in the row.
I have a word document that shows the screenshots, but I cannot attach it to this item.
Can you elaborate a little bit more on your scenario:
You edit a row(s) and then leave it by pressing “Done” button (this leads to style change showing that row is edited).
After that you scroll up/down and request new portion of rows.
Now you want when you scroll back up/down to previous portion of rows to have this edited row(s) with their changed style still applied.
Is this the functionality that you require?
Also do you commit the changes in these rows automatically or you batch them and commit them later on button click for example?
You should notice that when continuous virtualization is used current portion of rows is disposed and the required new portion is recreated when you scroll through the grid. This may be the main reason for the described by you behavior.