Description Richard Kulp 2002-02-19 11:12:43 EST

PropertySheetViewer.updateEntry() has a specific check for getting the image, 
and if the image is null, it will NOT set that into the item. This causes a 
problem. If the entry is being updated from having an image to not having an 
image, the old image stays there. The image being null is a valid setting and 
should be set through so that the entry no longer has an image.

PropertySheetViewer.updateChildrenOf(). If an entry was expanded and had 
children, and if the update indicates there are now no children, the entry is 
still marked as expanded. This doesn't cause a problem until the entry is 
updated again to have children, it is still marked as expanded.

The reason these have shown up is because it is very expensive to always use 
new PropertySheetEntrys when changing input. Deleting is especially expensive, 
it is very slow and very visible to the user when there are a lot of entries 
being deleted. So we were trying to reuse the PropertySheetEntries when the 
input changes. The above problems showed up because the entry was being reused 
but was referring to a different input. So the keeping the old image and the 
old expansion state are inappropriate.

Thanks.