Your Privacy Matters: We use our own and third-party cookies to improve your experience on our website. By continuing to use the website we understand that you accept their use. Cookie Policy
1085
Continuous virtualization editing problems
posted

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.

Parents
  • 15979
    posted

    Hello Karl,

    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.

Reply Children