I haven’t been able to nail this one down to be consistently repeatable, but it does happen for me:
Sometimes setting node.Image.Index doesn’t change the visual state. I’ve checked that it’s a valid index in the image list. I’ve even looked at the value of the Index after having called node.Document.UpdateViews(); and everything looks fine.
And it doesn’t seem to be an all-or-nothing prospect. When I change the index on several nodes, sometimes only some of them will display correctly.
Thoughts?
That sounds odd. I can’t recall hearing about anything like that. I assume you mean that when you change the index on several nodes to the same new index, sometimes only some of them will display correctly. Does the problem always happen with certain indices (images)?
I wonder if this is related to your other post (http://www.nwoods.com/forum/forum_posts.asp?TID=720). Maybe there’s some other code that is modifying your image unexpectedly.
[QUOTE=walter]Does the problem always happen with certain indices (images)?
I wonder if this is related to your other post (http://www.nwoods.com/forum/forum_posts.asp?TID=720). [/quote]
Interesting question - I’ll persue that. I wouldn’t be surprised if the two problems are related - I was hoping this symptom might have triggered a memory of something. I’ll keep investigating.
So far it looks independant of which index I use.
Solved - it was a bug in my code which uses a hashtable to manage nodes.