Bug 21522

Summary:	Selecting an interface in the java perspective then (new/class) does not fill in the interface on the new class dialog. Same thing works fine in java browsing perspective. [code manipulation]
Product:	[Eclipse Project] JDT	Reporter:	Dan Nazario <dan_nazario>
Component:	UI	Assignee:	Martin Aeschlimann <martinae>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	atsuiboupin
Version:	2.0	Keywords:	investigate
Target Milestone:	---
Hardware:	PC
OS:	Windows 2000
Whiteboard:

Description Dan Nazario

2002-07-12 09:15:51 EDT

Comment 1 Dirk Baeumer

2002-07-26 11:54:01 EDT

It does if you select an interface in the package explorer. If a CU is selected 
in the package explorer we "don't know" if it is an interface or a class.

Martin, do you think it is useful to look into the CU to figure out if it 
declares and interface or a type ?

Comment 2 Martin Aeschlimann

2002-09-16 08:30:17 EDT

Only when you select a Type, it is considered as a super interface or class.
On a CU, nothing is filled in.

This means you have the choice. We tried the otehr behaviour: CU are selected 
very often, what leads to many unwanted super interfaces/classes filled in.

Comment 3 Ats

2012-12-14 07:44:17 EST

(In reply to comment #2)
could you reconsider implementing it - i have a proposal...

> We tried the otehr behaviour: CU are selected 
very often, what leads to many unwanted super interfaces/classes filled in.

Probably this information shouldn't be filled in BY DEFAULT - maybe add a button to "New Java Class" dialog (for example next to [Browse] superclass or [Add] interface buttons) that tries to infer superclass and interface implementation from CU - i don't see downsides with this approach that made you to decide for "WONTFIX"