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 39259 - turn off confirmations for breakpoint and watch deletions
Summary: turn off confirmations for breakpoint and watch deletions
Status: CLOSED FIXED
Alias: None
Product: debugger
Classification: Unclassified
Component: Code (show other bugs)
Version: 3.x
Hardware: All All
: P1 blocker (vote)
Assignee: issues@debugger
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-01-27 09:15 UTC by Jan Jancura
Modified: 2010-04-29 09:16 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Jancura 2004-01-27 09:15:48 UTC 
Tor norbye:
-----------
 I'd really like an option to turn off
confirmations for breakpoint and watch deletions.
(Or if it's already there, make it easier to
find...)     I'm adding and deleting breakpoints
and watches all the time, as my interest shifts
from method to method as I'm debugging.  It makes
sense to ask the user "Are you sure" if the user
wants to delete a source file.  But a breakpoint,
or a watch, is a very transient thing, and not
something the user has invested a lot of work into
- so requiring confirmation just gets in the way.
Comment 1 _ tboudreau 2004-01-28 16:04:20 UTC 
if (Boolean.TRUE.equals(someNode.getValue("dontConfirmDelete")) {
  //just delete it
}

...?
Comment 2 Jan Jancura 2004-04-19 15:37:12 UTC 
fixed in the main trunk
Comment 3 Jan Jancura 2004-04-19 15:37:42 UTC 
fixed in the main trunk
Comment 4 Milan Kubec 2004-04-19 16:03:00 UTC 
Please, add cvs commit log. Thank you.
Comment 5 Marian Mirilovic 2009-10-01 14:49:12 UTC 
reopen to fix status and resolution
Comment 6 Marian Mirilovic 2009-10-01 14:51:50 UTC 
fix status and resolution
Comment 7 Quality Engineering 2010-04-29 09:16:09 UTC 
Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier.