Hello,
I am seeing a weird behaviour with the TreeListView where it appears that it is creating new items upon calling ExpandAll(). I am curious as to whether this is a known issue, or whether anyone else has seen this too.
I bind my TreeListView to a list that has a total of 87,954 rows. There are 18,493 top-level rows and the remainder are children (at various depths). I have exposed a button on the UI that simply calls ExpandAll() on the TreelistView. After this is clicked, the TreeListView displays a varying numbers of rows, all of which are greater than 87,954. Each time I launch the app and click the "expand all" button, I get different numbers of rows. I have seen 88,228, 88,232, 87,985 etc. - each of which is larger than the 87,954 as expected. I have confirmed that my bound collection has not changed, so I am lead to believe that somehow more items are being created during the expansion process. I have also noticed that if I try to scroll to the bottom of the TreeListView, it chokes and stops responding for some time before it will allow me to scroll to the bottom.
All these issues make me think that I am seeing a bug in the ExpandAll functionality. Can anyone confirm? (I am using the Q3, 2011 build. I will try the latest build shortly, but I am not at a point in our release where updating is possible.)
Thanks,
Mark
I am seeing a weird behaviour with the TreeListView where it appears that it is creating new items upon calling ExpandAll(). I am curious as to whether this is a known issue, or whether anyone else has seen this too.
I bind my TreeListView to a list that has a total of 87,954 rows. There are 18,493 top-level rows and the remainder are children (at various depths). I have exposed a button on the UI that simply calls ExpandAll() on the TreelistView. After this is clicked, the TreeListView displays a varying numbers of rows, all of which are greater than 87,954. Each time I launch the app and click the "expand all" button, I get different numbers of rows. I have seen 88,228, 88,232, 87,985 etc. - each of which is larger than the 87,954 as expected. I have confirmed that my bound collection has not changed, so I am lead to believe that somehow more items are being created during the expansion process. I have also noticed that if I try to scroll to the bottom of the TreeListView, it chokes and stops responding for some time before it will allow me to scroll to the bottom.
All these issues make me think that I am seeing a bug in the ExpandAll functionality. Can anyone confirm? (I am using the Q3, 2011 build. I will try the latest build shortly, but I am not at a point in our release where updating is possible.)
Thanks,
Mark
1 Answer, 1 is accepted
0
Hi,
Nedyalko Nikolov
the Telerik team
We are aware about this issue and we will make our best in order to fix it for the next internal build (Monday 2 April 2012).
Kind regards,Nedyalko Nikolov
the Telerik team
Sharpen your .NET Ninja skills! Attend Q1 webinar week and get a chance to win a license! Book your seat now >>