This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 108049 - Selecting the methods to override in the Generate Override Methods dialog impractical
Summary: Selecting the methods to override in the Generate Override Methods dialog imp...
Status: NEW
Alias: None
Product: java
Classification: Unclassified
Component: Source (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker with 1 vote (vote)
Assignee: Svata Dedic
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-06-25 17:17 UTC by Andrei Badea
Modified: 2015-10-02 14:21 UTC (History)
4 users (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

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 Andrei Badea 2007-06-25 17:17:06 UTC 
I wanted to override DefaultTableModel.getColumnClass(). The dialog opened up with DefaultTableModel expanded, but the
getColumnClass() method is in AbstractTableModel. I didn't realize that and just typed "getColumnClass" trying to quicky
select the method. Finally I realized I had to expand AbstractTableModel and select the method there.

The dialog should not force me to know where in the inheritance hierarchy is the method I want to override. I just want
a list of a methods logically defined in the current class. I guess the current approach probably has some advantages.
Then please introduce something like

[x] View Inheritance Tree

or

[o] Sort by Name    [o] Sort by Defining Class

at the top of the dialog.
Comment 1 Petr Hrebejk 2007-06-27 15:02:22 UTC 
Just for record: Nice way how to avoid this is to invoke code completion between methods.
Comment 2 Petr Hrebejk 2007-06-28 12:23:30 UTC 
I agree with the reporter. The override should rather be consistent with codecompletion way of doing it.
Comment 3 markiewb 2012-05-17 15:58:34 UTC 
Using NetBeans 7.2, you can select the wished item via keyboard. BUT the selection/filter only applies to currently opened treenodes. 

PROPOSAL: When starting to filter the tree should fully expanded before. Then it should work.