It would seem that i responded to that post as well, with basically the same advice: don't assign indexes to the LeftImages collection, so that the ImageList does not clone images. I don't know what else might have been causing you problems, but going by the age of that post I would think you should have received an answer about that by now.

Hello,

I have created following Case for you: CAS-57242-WYDQSQ

I will update you once I have more information for you.

Please do not hesitate to ask if you have any other questions.

So you guys know, I get this behaviour for any tree in my app that is using an imagelist. And we had a lot.

Is it possible the imae list is corrupted? I have another tree where I use the index and calling thousands of nodes with images and no issue like this. The test cases I showed you are with 3 or 4 nodes.

I changed everything to point to a resx file instead, and now no issue. But I had to rewrite our entire subsystem that checks the node index for rights and all. Had to go back and add a freaking has table to each node with the old index #. (we are already using the datakey, tag, and key property).

Also, any issue sharing the same image list with two trees? I was thnking about the value lists, and how I have to clone them to use in a data grid if I am using it on a drop down on the same form.