getting first root node of treeview

[Trucker]

Hi, I am using TreeView.TopNode to get the first root node of my treeview. This does not work for me all the time however. If you read the .NET Framework on this property, I think they state this also by saying: Initially, the TopNode returns the first root tree node, which is located at the top of the TreeView. However, if the user has scrolled the contents, another tree node might be at the top. I don't understand why the TopNode would return a different node after a user scrolled through the treeview.:confused: Does anybody know why? And in this case, how else could I get the first root node? Thanks. TraileR ParK LifE 4Ever

[David Crow]

One way would be to get the top node and save it in a member variable. That way you'll always have access to the top node no matter what amount of scrolling has transpired.

---

"One must learn from the bite of the fire to leave it alone." - Native American Proverb

[Jose Lamas Rios]

TopNode returns "the first fully-visible tree node in the tree view control". That is, it only considers those nodes that are currently visible, and that's why its result may vary if the user has scrolled. If what you want is the absolute first root node, I think it should be the first element of the collection you get through the Nodes propety. -- jlr http://jlamas.blogspot.com/[^]

[Trucker]

Thanks for the reply David. I simply chose to just get the first root node through the treeview.Nodes.get_Item(0) property, like Jose suggested but your way definitely works as well. Thanks. TraileR ParK LifE 4Ever

[Trucker]

Ofcourse! Here I go again thinking 'inside the box';P. Although I don't see the use of a function like TopNode that returns the first fully visible node... I mean cmon, who would want to get a node like that? Anyways, your answer is exactly what I was looking for. Thanks again:) TraileR ParK LifE 4Ever

[David Crow]

/*Trucker*\ wrote: I simply chose to just get the first root node through the treeview.Nodes.get_Item(0) property, like Jose suggested... Which is a much cleaner solution. I'm not familiar with the .Net stuff so some of my answers are not always straight forward.

---

"One must learn from the bite of the fire to leave it alone." - Native American Proverb