Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 293129 - New added resources are not filtered out
Summary: New added resources are not filtered out
Status: RESOLVED INVALID
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Resources (show other bugs)
Version: 3.6   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Serge Beauchamp CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 291755
  Show dependency tree
 
Reported: 2009-10-23 04:50 EDT by Szymon Brandys CLA
Modified: 2009-12-02 04:37 EST (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 Szymon Brandys CLA 2009-10-23 04:50:05 EDT 
Steps:
1) Add a project and assign "pattern matcher" filter to it (e.g. *.txt)
2) Add "a.txt" file to the project, it appears and is not filtered out
3) Refresh the project, now the file disappears
Comment 1 Serge Beauchamp CLA 2009-10-23 06:23:31 EDT 
Oh yes, this is by design.

It might not be intuitive, but the idea is that if the user explicitly creates a file under a folder that would normally be filtered out, this is for a reason - and the user is demonstrating his desire to override the filter for that single file.

This could be for a good reason, for example editing the file.

Once the user do a refresh local, it then disappears because of the filters being applied.

If this was not the case, it would be confusing for the user when he creates a new file, since it would not be able to edit it right away (as he can normally do with new files), having the new being open in an editor right after creation.

This also is in line with the general filter design, I believe, since its purpose is to show a subset in the workspace of the file system content.
Comment 2 Szymon Brandys CLA 2009-12-02 04:37:17 EST 
Marking as INVALID.