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.
Summary: | Add Breakpoint.getBreakpointType() | ||
---|---|---|---|
Product: | debugger | Reporter: | ivan <ivan> |
Component: | Code | Assignee: | issues@debugger <issues> |
Status: | CLOSED DUPLICATE | ||
Severity: | blocker | ||
Priority: | P3 | ||
Version: | 4.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
ivan
2004-08-12 02:37:43 UTC
Sorry to overload this rfe .... Along the same lines BT.getCustomizer() used to take a Breakpoint object in the 3.5 timeframe. Now it doesn't. I'm finding that the passed in bpt is handy to pre-populate the customizer when you're editing the breakpoint. If the passed in event is null then the customizer can allocate one. *** This issue has been marked as a duplicate of 47136 *** verified (the duplicate is still marked as new, so it should be resolved someday) To the BT.getCustomizer() - every Breakpoint implementation can have a BeanInfo. That BeanInfo is asked for a java.beans.Customizer and Customizer.setObject(Breakpoint) is called. This is what org.netbeans.modules.debugger.ui.actions.BreakpointCustomizeAction does. Are you saying "every Breakpoint implementation can have a BeanInfo" or "every Breakpoint implementation should have a BeanInfo" If the breakpoint wants to have enabled the standard "Customize" action in the Editor gutter then it should. Otherwise it just can. It was a convenient way how to add a Customizer without an API change. ;-) |