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.
Summary: | Enhancements to local variables view | ||
---|---|---|---|
Product: | debugger | Reporter: | _ sandipchitale <sandipchitale> |
Component: | Code | Assignee: | issues@debugger <issues> |
Status: | NEW --- | ||
Severity: | blocker | CC: | markiewb |
Priority: | P2 | ||
Version: | 4.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: | |
Attachments: | This view may give you an idea of what I am suggesting. Only thing is Object Explorer is reflection based tool and shows values in current JVM. (See contrib to try out ObjectExplorer). |
Description
_ sandipchitale
2005-04-03 06:37:17 UTC
Created attachment 21317 [details]
This view may give you an idea of what I am suggesting. Only thing is Object Explorer is reflection based tool and shows values in current JVM. (See contrib to try out ObjectExplorer).
Check out: http://blogs.sun.com/roller/page/scblog?entry=jpda_java_debugger_locals_view http://blogs.sun.com/roller/page/scblog?entry=jpda_java_debugger_locals_view1 OK, this is doable -> Will be considered. Note that it is already possible to directly modify values of primitive types and strings (just double click end edit the value in Local Var window). I would also like to see the popup actions to jump to the Declared type and the Actual type of the variables. Eclipse debugger supports all these functions. Set target-milestone of open issue to TBD (was < 7.3, f.e. 6.8), so the issue doesn't get lost. Set target-milestone of open issue to TBD (was < 7.3, f.e. 6.8), so the issue doesn't get lost. This time the target milestone is really set. |