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

Bug 97536

Summary:	[Import/Export] Import from archive should remember previous archive file
Product:	[Eclipse Project] Platform	Reporter:	Nick Edgar <n.a.edgar>
Component:	IDE	Assignee:	Platform UI Triaged <platform-ui-triaged>
Status:	RESOLVED DUPLICATE	QA Contact:	Prakash Rangaraj <prakash>
Severity:	enhancement
Priority:	P5	Keywords:	helpwanted
Version:	3.1
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Nick Edgar

2005-05-31 11:40:14 EDT

3.1 RC1

- File > Import > Archive file
- choose a previously exported archive file, and import it
- File > Import > Archive file
- the archive file field is blank

It should be the same as the previously entered one.
Notice that other import/export dialogs remember there settings from the previous time (but I believe 
this is only done if Finish is used, not Cancel -- should verify).

Comment 1 Nick Edgar

2005-05-31 11:41:21 EDT

Also, should ensure that pressing Browse when there's already a file name in the field opens on that 
file's directory.

Comment 2 Karice McIntyre

2005-08-22 17:18:09 EDT

The File system import also does not populate its combo with the selection from 
the last completed import.

Comment 3 Karice McIntyre

2005-11-18 10:20:51 EST

This doesn't appear to be a Mac-only issue.  Is the problem that we don't actually populate the combo 
with the last selected file or that we don't show the most recent selection (you have to drop down the 
combo to select it)?  If it's the former than this bug is fixed.  If it's the latter, then it is not fixed.

Comment 4 Karice McIntyre

2006-07-06 12:38:53 EDT

Nick, could you please comment on the question in comment #3?

Comment 5 Nick Edgar

2006-07-20 10:11:52 EDT

Populating the drop-down is fine.

Comment 6 Susan McCourt

2009-07-15 12:12:08 EDT

"As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009"

Comment 7 Prakash Rangaraj

2009-08-10 03:41:04 EDT


*** This bug has been marked as a duplicate of bug 266937 ***