Bug 21522 - 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]
Summary: Selecting an interface in the java perspective then (new/class) does not fill...
Status: RESOLVED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P3 normal with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Martin Aeschlimann CLA
QA Contact:
URL:
Whiteboard:
Keywords: investigate
Depends on:
Blocks:
 
Reported: 2002-07-12 09:15 EDT by Dan Nazario CLA
Modified: 2012-12-14 07:44 EST (History)
1 user (show)

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 Dan Nazario CLA 2002-07-12 09:15:51 EDT
Comment 1 Dirk Baeumer CLA 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 CLA 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 CLA 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"