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 56372 - [41cat] Form editor event method creation cannot stay in Design view to define multiple events.
Summary: [41cat] Form editor event method creation cannot stay in Design view to defin...
Status: NEW
Alias: None
Product: guibuilder
Classification: Unclassified
Component: Code (show other bugs)
Version: 4.x
Hardware: PC Windows ME/2000
: P3 blocker (vote)
Assignee: issues@guibuilder
Depends on:
Reported: 2005-03-14 13:09 UTC by lleland
Modified: 2008-04-28 22:14 UTC (History)
0 users

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description lleland 2005-03-14 13:09:36 UTC
[ BUILD # : Dev 20050314 ]
[ JDK VERSION : 1.5.0_01 ]

It is not possible to use the Event tab of the form editor Properties window to define a set of events all at once. When you click on an undefined event, an event method name is automatically generated. When you type return, type tab, or click on another event, the file view is immediately flipped to Source view and the cursor positioned at the new event method. You cannot stay in Design view to define more events.

It would be more effective if the view only changed to Source view when return is typed or the field is double-clicked. If you either type a tab or click on another event, the new event code should still be generated, but the view should stay in Design view and the focus moved to the next or clicked event. This would enable the user to define a set of related events all at once, and then flip over to the Source view to edit them just once.

As it is now, you have to flip back and forth between Design and Source views for each event method one at a time.
Comment 1 Jan Stola 2005-03-14 13:21:45 UTC
Request for enhancement => changing issue type.
Comment 2 Tomas Pavek 2005-05-13 14:30:10 UTC
Creating an event handler brings you to the source editor. With the currrent
implementation based on property sheet we can hardly distinguish how the value
was added (whether Enter was pressed or the field was just left by clicking
somewhere else).
Comment 3 Tomas Pavek 2005-05-16 16:48:50 UTC
See also issue 23069.
Comment 4 lleland 2008-04-28 22:14:24 UTC
I'm glad to see this design bug (not enhancement) is under review for an upcoming release.

It is so simple to fix as I stated in my initial post, and it is a royal UI pain-in-the-butt.