5 Answers, 1 is accepted
We are not aware of similar issue in the RadTreeView. Having so much hierarchy levels could lead to serious performance downgrade but not an exceptions. What is the exception that you have come up with? Is it possible for you to isolate a scenario in a runnable application that reproduces it ? This will be highly appreciated and we would be better able to assist you.
All the best,Petar Mladenov
the Telerik team
Explore the entire Telerik portfolio by downloading the Ultimate Collection trial package. Get now >>
XAML code :
<telerik:RadTreeView x:Name="treeView" IsVirtualizing="True" telerik:TreeViewPanel.VirtualizationMode="Hierarchical"
IsLoadOnDemandEnabled="True" LoadOnDemand="treeView_LoadOnDemand">
<telerik:RadTreeViewItem Header="1" IsLoadOnDemandEnabled="True"/>
</telerik:RadTreeView>
code behind :
private void treeView_LoadOnDemand(object sender, Telerik.Windows.RadRoutedEventArgs e)
{
RadTreeViewItem item = e.OriginalSource as RadTreeViewItem;
item.Items.Add(new RadTreeViewItem() { Header = int.Parse(item.Header.ToString()) + 1, IsLoadOnDemandEnabled= true });
item.IsLoadOnDemandEnabled = false;
item.IsLoadingOnDemand = false;
item.BringIntoView();
}
You will see that after you try expanding 56/57/58 rth item it throws an exception.
We investigatde this further and it appeared that there is a limitation in the number of nested elements that comes from the Silverlight Framework. This number varies depending of the type of the elements. We made a small test that shows that you cannot nest more than 80 Buttons for example. So, the exception that raises when having 50-60 nested RadTreeViewItems is expected.
Please accept my apologies for any inconvenience caused previously.
Petar Mladenov
the Telerik team
Explore the entire Telerik portfolio by downloading the Ultimate Collection trial package. Get now >>