Bug 164082 - [CommonNavigator] : Color of a tree node is not refreshed when parent is refreshed
Summary: [CommonNavigator] : Color of a tree node is not refreshed when parent is refr...
Status: RESOLVED DUPLICATE of bug 261147
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Francis Upton IV CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2006-11-10 04:24 EST by Emil Richard CLA
Modified: 2009-02-10 03:46 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Emil Richard CLA 2006-11-10 04:24:05 EST
I have extended the Common Navigator. Its labelProvider implements IColorProvider.

  I have to populate the server status in the tree.The tree changes the image and text according to the server Status (say connected and disconnected). When the server is in disconnected state, I make the color of the server (foreground color) as red.  But this color change is not reflected in the tree after refreshing for the first time ..It refreshes randomly.I use TreeViewer.refresh(element,true) 

  I am using eclise 3.2.1 WTP Build id: M20060921-0945  to develop RCP application.

I also went through a bug posted in the http://bugs.eclipse.org

https://bugs.eclipse.org/bugs/show_bug.cgi?id=125575

The status of the bug says fixed , but I find problems.The color is not refreshed in the same flow as in the case of Image and text .
Comment 1 Michael D. Elder CLA 2006-12-03 20:57:21 EST
Could you provide an isolated test case that shows the problem (a JUnit test would be best). 

Do you see the same behavior with update(<server>) ?
Comment 2 Francis Upton IV CLA 2009-01-29 15:37:53 EST
Can you try this in 3.5M5?  There have been several fixes in this area that might have fixed this.
Comment 3 Francis Upton IV CLA 2009-02-10 03:46:20 EST

*** This bug has been marked as a duplicate of bug 261147 ***