Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 367179

Summary:	[Import/Export] Import from Filesystem allows to filter based on file extensions: Improve the workflow for doing that
Product:	[Eclipse Project] Platform	Reporter:	Helmut J. Haigermoser <helmut.haigermoser>
Component:	UI	Assignee:	Platform-UI-Inbox <Platform-UI-Inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	enhancement
Priority:	P3
Version:	3.7
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:	stalebug

Description Helmut J. Haigermoser

2011-12-20 07:48:42 EST

Build Identifier: 

The "Import from file system" wizard allows to select specific file extensions for importing which is a nice feature. However, there are some scenarios that are not covered nicely as of know:
- No feedback if a selected file type is not available
- Too many file types selectable initially

The dialog allows to specify a directory to import from, but the selection of file types to chose from is static. The sheer amount of file types is overwhelming, especially so if the tree only includes two or three types. 
Ideally we could scan the directory and offer only those types for selection that are there...

But as a start this bugzilla requests to bring up a message describing what types were found and which ones were not after acknowledging the filter and filtering:
- 1 file for type "*.c" found
- 0 files for type "*.h" found

Let me know what you think !:)
Helmut

Reproducible: Always

Steps to Reproduce:
1.Import from File system
2. Specify a directory with one .h file
3. Push "Filter Types...",  filter for "*.c": Finish is enabled without actual content
4. Push "Filter Types...",  filter for "*.c" and "*.h": Finish will import a single .h file

Comment 1 Helmut J. Haigermoser

2011-12-20 07:49:13 EST

CQ:WIND00084556

*setting version to 3.7.1*

Comment 2 Lars Vogel

2019-11-14 03:48:47 EST

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.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.