Suppose I have a method and I don't want to step into it. If I set a breakpoint at the line following the method and then press F5, the method takes a reasonable amount of time to execute. However, if I press the F8 key (a mistake I always regret when the method does a lot of stuff like iterating over large datasets etc.) the debugger ends up doing huge amounts of work and taking orders of magnitude more time. The same once I trace into a method and then decide I want to step back out using ctrl-F7. When I bring up the windows task manager and look at the cpu%, the netbeans debugger, not the app I am debugging is consuming the cpu.

Either F8 or ctrl-F7 should be redone to act as though a breakpoint was set on the line following the method I either chose to step over or trace into.

Although this may seem like a small problem, it is a pretty big deal from the standpoint of debugging efficiency. Also it seems as though it would be fairly straighforward to modify, giving a pretty big payoff for maybe not much work.

thanks