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 186659 - Display value of String instances naturally
Summary: Display value of String instances naturally
Status: RESOLVED DUPLICATE of bug 96212
Alias: None
Product: profiler
Classification: Unclassified
Component: Ide (show other bugs)
Version: 7.0
Hardware: All All
: P2 normal (vote)
Assignee: issues@profiler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-25 12:29 UTC by Jesse Glick
Modified: 2010-06-02 08:57 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments
Proposed patch to display String values directly just like char[] (3.54 KB, patch)
2010-05-25 12:29 UTC, Jesse Glick
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Jesse Glick 2010-05-25 12:29:44 UTC
Created attachment 99432 [details]
Proposed patch to display String values directly just like char[]

Currently the Profiler displays in the Value column the actual value of a char[]. But for a String it just displays "#123456" or similar; you have to expand the node to look at the 'value' field.

This can make certain workflows vastly slower than they need to be. For example, recently I had a heap dump with 88 instances of a kind of Node; most had a String stored in the name or displayName slot. I was looking for a certain one. 88 times, I had to click the Node instance on the left, then move the mouse over and click the expand handle next to displayName to see the value. If I could "see" String's directly, I could just click on #1, look at the Value column next to displayName, then just press the Down key until I found it, saving myself several minutes and some joint pain in my fingers.

I am attaching a patch which appears to work well.
Comment 1 Tomas Hurka 2010-05-25 13:03:48 UTC
For your use-case it is much easier to write OQL query.

*** This bug has been marked as a duplicate of bug 96212 ***
Comment 2 Jesse Glick 2010-05-25 13:58:52 UTC
Well, clicking Down 88 times is easier than looking up OQL syntax and trying to write and debug a query. It would be useful if there were 800 or 8000 instances. Anyway this was just one example of a use case.
Comment 3 Tomas Hurka 2010-06-02 08:57:17 UTC
(In reply to comment #2)
> Well, clicking Down 88 times is easier than looking up OQL syntax and trying to
> write and debug a query. 
.. but you can use OQL in a lot of different situation, so I think that it is a good idea to know something about OQL. The OQL help is available online here: <https://visualvm.dev.java.net/oqlhelp.html>