Bug 48119 - [Navigator] file icons are not updated when file associations are modified.
Summary: [Navigator] file icons are not updated when file associations are modified.
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.0   Edit
Hardware: PC All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Francis Upton IV CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-12-04 17:08 EST by Luc Bourlier CLA
Modified: 2019-09-06 16:13 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Luc Bourlier CLA 2003-12-04 17:08:05 EST 
I20031203

1. launch Eclipse on a new workspace
2. create a project
3. create a file named 'test1.xml'
The new file is displayed with the default (text) file icon.
4. associate '*.xml' files to the ant editor in
window>preferences>workbench>file associations
5. create a file named 'test2.xml'
The new file is displayed with the ant file icon, test1.xml is still displayed
with the default file icon.

Closing/re-opening the view solves the problem.
Comment 1 Debbie Wilson CLA 2003-12-08 10:27:19 EST 
Which view are you opening/closing?  Navigator?  Package Explorer?  ...
Comment 2 Luc Bourlier CLA 2003-12-08 11:07:44 EST 
I tried with the Navigator and with the Package Explorer, the result is the same.
Comment 3 Nick Edgar CLA 2003-12-08 18:01:42 EST 
This is a general problem with all navigator-like views, not just the Navigator.
Would need some kind of notification from the editor registry that the file 
associations had changed.  The relevant label providers would have to listen 
for changes, e.g. WorkbenchLabelProvider.
Comment 4 Eclipse Webmaster CLA 2019-09-06 16:13:57 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.