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 33286 - Remove button in New Wizard's Override Inherited Methods screen doesn't work
Summary: Remove button in New Wizard's Override Inherited Methods screen doesn't work
Status: RESOLVED WONTFIX
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 3.x
Hardware: Other Linux
: P4 blocker (vote)
Assignee: issues@java
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-04-28 23:47 UTC by davidc11
Modified: 2007-09-26 09:14 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
My ide.log file when the error occured. (12.15 KB, text/plain)
2003-05-06 19:04 UTC, davidc11
Details

Note You need to log in before you can comment on or make changes to this bug.
Description davidc11 2003-04-28 23:47:39 UTC
Create a new class using the Java Class template.  
Hit the "Next" button in the New Class Wizard until the Override 
Inherited Methods screen appears. 
Select a method from the Object class and add it to list of 
overridden methods. 
Select the method in the "Methods to be Overridden" list, at this 
point the "Remove" button should be activated but it stays greyed 
out. 
You can still clear the methods to be overridden list by clicking 
on the remove all button. 
 
I'm using the 3.5 beta release on Redhat 7.2 with blackdown 1.4.
Comment 1 pzajac 2003-04-29 08:43:41 UTC
reassigned to java 
Comment 2 Jan Becicka 2003-04-29 10:07:36 UTC
This is valid bug. Remove button is not enabled, but only "sometimes".
Workaround exists: select another method and then reselect method you
want to remove. Remove button gets enabled.
Comment 3 davidc11 2003-05-06 19:04:30 UTC
Created attachment 10233 [details]
My ide.log file when the error occured.
Comment 4 davidc11 2003-05-06 19:05:34 UTC
Sorry, I uploaded the ide.log for the wrong issue.  
Comment 5 Jan Pokorsky 2003-12-02 10:59:21 UTC
As a consequence of the issue #35601 this has become irrelevant.