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 126242 - Allow Enable/Disable/Delete All breakpoints directly from Design view
Summary: Allow Enable/Disable/Delete All breakpoints directly from Design view
Status: VERIFIED FIXED
Alias: None
Product: soa
Classification: Unclassified
Component: BPEL Debugger (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Kirill Sorokin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-01-30 02:40 UTC by lpolycarpou
Modified: 2008-02-07 09:21 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description lpolycarpou 2008-01-30 02:40:49 UTC
From the design view, we currently have the ability to Toggle Breakpoints individually at various scopes (including the
process itself) and on different activities.  Once these breakpoints are set, these can be removed by toggling off
(Right-click and select Toggle Breakpoints or just highlight and use CTRL-F8).

This ticket is for an enhancement request to allow all breakpoints to be quickly and easily deleted, disabled or
re-enabled.  This can apply either to within a particular selected scope or at the process level to apply to all
breakpoints in the BP.

Similar functionality is available in the Breakpoints window (hence the lower priority of this ticket) but adding these
three options will improve usability in my opinion.
Comment 1 Sergey Lunegov 2008-01-30 09:22:41 UTC
Don't see easy way to implement it in Sierra.
Comment 2 Kirill Sorokin 2008-02-01 10:19:40 UTC
I have added three additional buttons to the design view toolbar -- Enable/Disable/Delete breakpoints. Pressing either
of them will lead to enabling/disabling.deletion of all breakpoint on/within the selected element. If no element is
selected the whole process becomes the scope of these actions.

I hope this does resolve the issue.
Comment 3 Ivan Sidorkin 2008-02-07 09:21:39 UTC
verified in NetBeans IDE Dev (Build 200802060003)