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 123930 - "New breakpoint ..." action context issue
Summary: "New breakpoint ..." action context issue
Status: CLOSED FIXED
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 6.x
Hardware: All All
: P4 blocker (vote)
Assignee: issues@debugger
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-12-13 09:26 UTC by Jiri Vagner
Modified: 2010-04-29 09:37 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jiri Vagner 2007-12-13 09:26:31 UTC
User can call action "New breakpoint..." and invoke "New Breakpoint" dialog from "Run" main menu and from popup menu
inside Breakpoints window. If cursor inside java code is placed somewhere inside method body, dialog invoked using "Run"
menu will contains class name, method name and type will be set to "method" breakpoint.

It is cool, but dialog invoked via popupmenu inside Breakpoints window doesn't contain this cute context AI. For users
(specially for beginners) this should be confusing - same dialog invoked using same menu item "New Breakpoint..." but
with different content...

From my point of view using "New breakpoint.." from Breakpoints windows is more easy, more direct and for beginners more
intuitive way than using action from Run menu. Please use cute context AI also for second use case. ;)
Comment 1 Petr Cyhelsky 2008-09-18 08:52:08 UTC
As of now, on:
Product Version: NetBeans IDE Dev (Build 200809180201)
Java: 1.5.0_15; Java HotSpot(TM) Client VM 1.5.0_15-b04
System: Windows Vista version 6.0 running on x86; Cp1250; cs_CZ (nb)

this works - even when the new breakpoint dialog is invoked from breakpoints view popup the "cute context AI" works fine.
It must have been fixed in the meantime.
Comment 2 Martin Entlicher 2008-09-18 09:31:12 UTC
x
Comment 3 Martin Entlicher 2008-09-18 09:31:42 UTC
Yes, this was fixed together with issue #147304.
Comment 4 Quality Engineering 2010-04-29 09:37:28 UTC
Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier.