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 7745 - Too hard to remove an accidentally created event method
Summary: Too hard to remove an accidentally created event method
Status: CLOSED FIXED
Alias: None
Product: guibuilder
Classification: Unclassified
Component: Code (show other bugs)
Version: 3.x
Hardware: All Windows 3.1/NT
: P4 normal (vote)
Assignee: issues@guibuilder
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2000-09-23 01:18 UTC by jhoffman
Modified: 2003-06-30 18:27 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Error log for Null Pointer exception (6.70 KB, text/plain)
2000-12-06 10:17 UTC, Marian Mirilovic
Details

Note You need to log in before you can comment on or make changes to this bug.
Description jhoffman 2000-09-23 01:18:46 UTC
It is too easy to create spurious event methods in form code just by double
clicking on a component on your form.  It needs to be easier to remove these
unwanted methods.  For example, you should be able to clear out the event handler
name in the properties sheet on the "Events" tab in order to remove the method from
the code.  Currently, you must click the ... button and then select the
method name, then click the Remove button, the OK button and then the OK button
on the warning message that appears.

It would be fine to have a warning message when you clear out the event handler
name in the properties sheet, but the warning should really only appear if there
is code in the method that you're going to delete.  Otherwise, the message is
not necessary.
Comment 1 Jan Stola 2000-09-25 08:22:59 UTC
*** Bug 7746 has been marked as a duplicate of this bug. ***
Comment 2 Marian Mirilovic 2000-12-06 10:12:59 UTC
Next problem is with work with event ( rename, add , remove ) , here is some
problems ,
if you open Handlers dialog for event( you must click ... button) , you will see
table with name of handlers, if you rename some handler and its new name is
"aaaaaaaaaaaaa" and after change, you rename again the same handler as
"bbbbbbbbbbbb" and  click the OK button , you obtain Null Pointer Exception.

And next problem is conformable if you first rename handler and remove the same
handler , the handler is removed from table in Handler event window, and if you
click the OK button , in the Source editor is handler only renamed.
Comment 3 Marian Mirilovic 2000-12-06 10:17:59 UTC
Created attachment 378 [details]
Error log for Null Pointer exception
Comment 4 Tomas Pavek 2000-12-06 17:07:59 UTC
Fixed in main trunk and release31 branch.
Comment 5 Marian Mirilovic 2000-12-18 14:12:59 UTC
verified in [main-trunk](91) and [release31](30)

part of rename Event Handlers
still open in version : FFJ20
Comment 6 Marian Mirilovic 2001-01-23 09:50:59 UTC
BUG also appears in version : FFJ20
Comment 7 Quality Engineering 2003-06-30 18:27:50 UTC
Resolved for 3.3.x or earlier, no new info since then -> closing.