Bug 201453 - [Preferences] [FieldEditors] Directory and File FieldEditor enhancement - Combo box
Summary: [Preferences] [FieldEditors] Directory and File FieldEditor enhancement - Com...
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.4   Edit
Hardware: PC Windows XP
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2007-08-28 13:52 EDT by Pierre Carlson CLA
Modified: 2019-09-06 16:08 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pierre Carlson CLA 2007-08-28 13:52:45 EDT
Build ID: I20070821

The DirectoryFieldEditor and FileFieldEditor classes are proving to be very useful.  One problem I have is that the method to browse to and find a file or directory can be very time consuming.  A good amount of the time is me trying to remember what I am looking for at the moment, but also following long paths can take some time. Generally, I use these editors to switch back and forth between the same 4 or 5 files or paths.  It would therefore be a useful enhancement to allow the use of a Combo instead of just a Text field.  The Combo box could store a configurable number of choices as a history of the files/directories previously selected.  The browse button could be used to add a new choice to the list and set it as the first item.  This effect would be something similar to how the PDE target platform preference works now.  

Also important, the combo box should allow copy/paste to add paths and files.  If I have a path opened in windows explorer, copy/paste is much faster than browse.  

I would also want to default the combo to some predefined list.
Comment 1 Eclipse Webmaster CLA 2019-09-06 16:08:24 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.