Hello
We are using the RadGridView to show hierarchical data X levels deep. Typically this is only used up until 5 or 6 levels deep.
We use the RowChildTemplate where we define other radgridviews that display the collections of children (loaded on demand)
Now, the problem is that when we expand a top level node that has a lot of items (2000+), it takes a very long time for the UI to update (> 2 mins) and afterwards the application is very unresponsive + takes up a lot of memory. I have a suspicion this is because the child gridview containing the 2000+ items is actually in the first row, of which a part is shown in the UI obviously. So even if only the top row + 2 or 3 rows of the child gridview is visible in the UI, the other 2997 rows of the child gridview are still instantiated because they are "part of" the top level row so virtualization is not used on "sublevels".
Is this a known problem and do you (or anyone) perhaps have a workaround for this? This is a blocking problem for us...
We are using the RadGridView to show hierarchical data X levels deep. Typically this is only used up until 5 or 6 levels deep.
We use the RowChildTemplate where we define other radgridviews that display the collections of children (loaded on demand)
Now, the problem is that when we expand a top level node that has a lot of items (2000+), it takes a very long time for the UI to update (> 2 mins) and afterwards the application is very unresponsive + takes up a lot of memory. I have a suspicion this is because the child gridview containing the 2000+ items is actually in the first row, of which a part is shown in the UI obviously. So even if only the top row + 2 or 3 rows of the child gridview is visible in the UI, the other 2997 rows of the child gridview are still instantiated because they are "part of" the top level row so virtualization is not used on "sublevels".
Is this a known problem and do you (or anyone) perhaps have a workaround for this? This is a blocking problem for us...