Bug 71726 - C/C++ Projects view doesn't display changes in .* files
Summary: C/C++ Projects view doesn't display changes in .* files
Status: RESOLVED FIXED
Alias: None
Product: CDT
Classification: Tools
Component: cdt-core (show other bugs)
Version: 2.0   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: 2.0.1   Edit
Assignee: Alain Magloire CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-08-10 13:41 EDT by Aaron Luchko CLA
Modified: 2009-01-09 14:57 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Aaron Luchko CLA 2004-08-10 13:41:55 EDT
Description of problem: 
In the C/C++ Projects view try adding/deleting/renaming a .* file in a
C/C++ project, the view will not record any change, ie if you add .foo
it won't show up, if you delete .foo it will still show up, if you
move .foo to .bar .foo will still be the displayed name for the file.
 The changes are made correctly in the file system.  I've encountered
similar behavior with files without .* names but with less certainty,
it seems to happen only once you've tried moving around .* files. 
However if you attempt the same actions on a Java Project in the C/C++
Projects view they will works as intended.


Version-Release number of selected component (if applicable): 
2.0

How reproducible:
Always


Steps to Reproduce:
1. Create new C project, Standard Make Project and switch to C/C++
perspective as prompted and "C/C++ Projects" view
2. Create new File, ".foo" in project
3. Turn off filter for .* and look in project.
  
Actual results:
.foo is not listed, other .* files are (.cdtproject, .project)

Expected results:
.foo should be listed with other .* files

Additional info:
To get the changes to show up you can close and reopen the project.  Adding
other .* files and renaming an existing .* file will be similarly not updated.
Comment 1 Alain Magloire CLA 2004-08-16 10:40:20 EDT
Yes I believe it was fix in the head and the branch

Please try a newer build and let me knwo if the problem is fix.
making this 2.0.1 target
Comment 2 Aaron Luchko CLA 2004-08-16 12:05:59 EDT
Just checked against CVS head and the bug was fixed. 
thanks