Bug 198432 - Prioritization/categorization of event handlers
Prioritization/categorization of event handlers
Status: NEW
Product: guibuilder
Classification: Unclassified
Component: Code
7.0
All All
: P3 (vote)
: TBD
Assigned To: issues@guibuilder
issues@guibuilder
et_5
: PLAN
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-05-08 15:12 UTC by Jan Stola
Modified: 2013-09-04 13:46 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Stola 2011-05-08 15:12:58 UTC
The current version of GUI Builder doesn't have any categorization of event handlers. All event handlers are just sorted alphabetically and presented to the user. This works somehow only because the most important event handler (actionPerformed) is the first in the alphabet. But there are components whose the most important handler is buried deep in the list, for example stateChanged handler of JSlider.

It would be nice to categorize the event handlers in a similar way as properties are categorized. Also it would be helpful to modify Events menu to have the most important event handlers at the top.

There are several methods that claim to provide the required info:

BeanInfo.getDefaultEventIndex()
EventSetDescriptor.isInDefaultEventSet()
EventSetDescriptor.isExpert()
EventSetDescriptor.isPrefered()

Unfortunately, these methods don't seem to return any useful information when called on default BeanInfo(s)/EventSetDescriptor(s).


By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo