Hi together!
I want to make a subset of nodes in an UltraTree visible and invisible via a checkbox in the application. The tree is bound to a DataSet. I switch visibility of the nodes via the UltraTreeNode.Visible property. I DO NOT touch the data source!
After switching the nodes invisible and then back to visible, the position of the node(s) are not correct anymore. Please see the images below to see the problem. Is there any way to fix the nodes position?
1. The Holiday-nodes are in the correct order:
2. Now, we switch the Holiday-nodes to invisible:
3. And switching Holiday-nodes back to visible:
As you can see, the Holiday Taken (nominal)-node is not at the position at it is in the first image.
How can I ensure the nodes position?
Thanks a lot for your help!
Best regards,
Robin
Yes, I tried it with the controls version 11.1 and it works fine! Thanks a lot!
Hi Robin,
I ran your sample and I am able to see the problem as you describe. But I noticed that the problem only affects the display. If I add code to the CheckedChanged event to loop through the nodes, I can see that the Nodes collection is in the correct order.
In any case, this looks like a bug in the old version of the control you are using. I updated your sample to the oldest currently-supported version (11.1) and it works fine. So this issue is already fixed.
Hi Mike!
Thank you very much for you reply and please excuse my late one.
We are using version 9.1.
Nice to hear, that the Visible property should not affect the nodes position, but it seems like this, as you can see in the attached example you asked for. You can find the assemblies we are using in the zip archive, too.
If you click the checkbox in the example project, some nodes are set to invisible. If the nodes are set back to visible, it seems that positions are changed. Maybe the last node is not correctly repositioned?
What can we do?
Thanks a lot!
What version of the tree are you using?
The Visible property should never affect the position of the nodes. So if this is happening in the latest version of the tree and it's not the results of something in your code that is changing the position of the items in the list, then it's a bug in the tree.
Can you post a small sample project demonstrating this behavior so we can check it out?