I created a test application I put URL at bottom. I am getting weird behavior. The situation is that we have a dynamic workflow that the treeview will read at runtime, ondemand. So the workflow for all the same type objects is the same, which seems to throw off the treeview. So follow these steps and you should see what I mean:
1) Expand "Arrow Canyon" and select a child node "Comment"
2) Now expand another section like "Buck Mountain". Notice that "Comment" is already selected just like the first section.
3) Now select a different child item under "Buck Mountain", like Reference. Notice what changes is the items under "Arrow Canyon".
So even though they are different instances, it always acts like you are working with the first instance. And in fact, in my program I am writing, every reference is to the first section, no matter which instance I am using.
I figured it had something to do with each node using the same workflow. But they are different instances, so I assumed this would be fine. Perhaps you could educate me on how I should be using this correctly so only one item is selected at a time and it is in the correct section?