Hello,
I have a serious issue with the designer for the tree control..if I click on Nodes in the properties tab to create some nodes design time...after I click OK, even if I don't add anything..it removes the first node and all it's children. If I click nodes again, then ok without even doing anything (add removing nodes) it does the same thing.
Sorry, should add that I am using VS 2010, with the the Infragistics 2010 Vol2
The only reason I can think of for behavior like this is if you are using an inherited form with a tree on the base form. Is that the case? If so, then you cannot modify the nodes collection on the child form - the form designer simply can't handle it.
Well it is not happening so far on the ton of other trees we are using. So I just removed it and recreated from scratch and the issue went away.
Just as an interesting side note tidbit. A while back I had a long back and forth about the nodes and the left images collection where I wanted to test for WHAT image it was during a drag over event. I think I finally finally understand what is going on. In that discussion I learned that in ordrer to correctly user the image list, it should be .LeftImages.Add(1) ..where 1 is the index from the image list.
By accident I discovered that when you do this, you can cast LeftImages[0] to Int32..and it will return the image index hurray.
However when I set a node up at design time, and point LeftImages through your designer to Lets say ImageList item 0....in the code designer form you guys put .LeftImages.Add("picture.png') instead of the actual image. So I guess however the image is being set you are just casting it from object and storing it. I was able to fix the problem by editing the designer code myself...just as an FYI I guess.
Hi,
I tried this out and it works just fine for me. Does this happen if you create a new project and put a tree on a form? Or does it only happen on one particular form?
If it happens with a new tree, then I'm baffled - I've never heard of anything like that happening before.
If it only happens with one particular tree on one particular form, then my guess is that it's a bug related to something on the form or perhaps some property setting or combination of property settings.If thta's the case, maybe you could copy that form into a new project (or just copy the project and remove everything but the one form) and post it here so we can check it out.
No, we are not using visual inheritance.
What I meant by that it used to work was that nothing in the code has changed. We moved the controls from 9.2 to 10.2.20102.2026 and now we have this issue with the designer.
So, do I take it from your response that you are not using visual inheritance to derive from a form with a tree on it? Or are you saying that you are doing that, but it used to work?
This only started happening after I upgraded the controls to 10.2.20102.2026 with VS2010.
If I go back to VS2008 with the 9.2 controls, I don't have this issue.