Hi,
I am using Binding List concept to create Node List and assigning this Node List to the DataSource of the WinTree as mentioned in the Post http://forums.infragistics.com/forums/t/5222.aspx
I am facing following issue:
1. How can I hide the particular nodes from WinTree before assigning to the DataSource of the WinTree?
2. Leaf nodes showing ‘+’ even though it doesn’t have Children.
3. If I create WinTree object dynamically at runtime and bind the Node List to DataSource of it, ‘ExpandAll’ doesn’t work.
Thanks in advance.
Kumar
Hi Brian,
Please refer attached source code for exact scenario for issue #3, in which ExpandAll is not working.
In the attached source code, I am using MVP architecture. I have used ExpandAll in Bind() method of TreeView Class and calling this Bind() method from TreePresenter class.
Thanks in advance,
Thanks for your solution.
Please find below the Issues with above Solutions:
Solution 1: This works for me, but i have to set manually the Visible property of each Node. Will this affect the performance? Does this have any other option?
Solution 2: This works for me.
Solution 3: Please find the sample source code ( SampleUltraTreeLoaderFromList.zip ) for your reference as attachment.
Thanks in advanced,
1. You can't. UltraTreeNode exposes a Visible property, but you can't get a reference to a node that will represent a list object from the data source until the data source has been assigned. Once it has, the InitializeDataNode event will fire for each node; you can set the Visible property to false for the node therein.
2. To optimize performance by deferring the loading of child rows until they are requested, the ShowExpansionIndicator property resolves to 'CheckOnExpand', which causes them to appear for all root nodes regardless of whether they have children. You can switch this off by setting UltraTree.Override.ShowExpansionIndicator to 'CheckOnDisplay' instead, but note that by doing so you might be introducing a performance hit when bound to relatively large datasets.
3. I could not reproduce this behavior with a simple test. If possible post a code sample or test project that demonstrates the problem and we can take a look.