Bug 87235 - Better Access for Class, Method, Variable, Exception Breakpoints
Better Access for Class, Method, Variable, Exception Breakpoints
Status: NEW
Product: debugger
Classification: Unclassified
Component: Code
5.x
All Windows ME/2000
: P3 (vote)
: TBD
Assigned To: issues@debugger
issues@debugger
: USABILITY
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-10-16 19:10 UTC by tomzi
Modified: 2011-02-22 23:54 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 tomzi 2006-10-16 19:10:51 UTC
I just found out, after years of using Netbeans, that there also exist class,
method, variable, exception bp... It would be a great usability extension to
create those breakpoints out of the cursor context in the editor. E.g. if you
select a method -> new method exception. Same with variables, class and
exception. That would save a lot of typing when using 'New Breakpoint' in
Breakpoints view.
Comment 1 Jiri Kovalsky 2006-10-16 19:30:09 UTC
Well, I am sure this is already implemented and you just didn't discover the
feature. If your cursor is located somewhere in the method signature and you
invoke "Run|New Breakpoint..." from the main menu, the dialog comes up with all
the fields already prefilled. Please confirm if this is what you wanted.

Thanks for your feedback.
Comment 2 Roman Ondruska 2006-10-16 20:53:22 UTC
Jirko, thanks for the evaluation. Anyway, this is RFE not DEFECT.
Comment 3 Martin Entlicher 2006-10-17 11:20:25 UTC
IMHO Tomzi means to have a way how to create method/class/exception/variable
breakpoints directly from the Editor, like it's described in issue #43066?

The current state does not seem to be usable enough, according to the complaints
we are receiving.
Comment 4 tomzi 2006-10-17 12:00:17 UTC
Oh, got ya, thanks for the hint - I didn't try run/new breakpoint there ever
before... :)

I looked first in bp-view and there 'New Breakpoint' didn't prefill the values.

The current alorithm to find out where the cursor is placed seems to be too
simple. Since eg
everything i select is recognized to be a variable, this should be more context
sensitive! Opened a RFE for this bug #87288.

However, i still think it would make sense to put some context-sensitivity for
breakpoint creation into the context-menu. Like

.) 'New Class BP', if cursor is placed on classname or wihtin classcope, but not
in method scope
.) 'New Method BP', if cursor is placed only in the method signature
.) 'New Variable BP', if cursor is placed on a variablename.
.) 'New Exception BP', if cursor is placed on an Exception.
.) 'New Line BP', if cursor is in method scope(,...) and not placed on a
classname, variable, exception.

Only one option should show at the same time. Additionally the 'Toggle
Breakpoint' should then be renamed to 'Toggle Line Breakpoint' to distinct it
from the other breakpoints 

You could also have them all work like 'Toggle Breakpoint' eg. named 'Toggle
Method Breakpoint' and then be customizable like in 'Toggle Breakpoint'.
Comment 5 pekarna 2011-02-22 23:54:36 UTC
This is quite old but still NEW - I don't see Run->New Breakpoint, was this RFE completed?


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