|
|
|
Re: View object values in a View [message #652237 is a reply to message #652056] |
Thu, 03 February 2011 10:06 |
Iulian Dragos Messages: 23 Registered: July 2009 |
Junior Member |
|
|
Jonathan Lawrence wrote on Wed, 02 February 2011 09:39 | Hi Iulian
I'm not clear exactly what you mean by the resolved value of an object because surely that is just the fields which comprise the object, with their values. In general that is as much as can be displayed for an object, except for some special cases where the tool will display internal values (eg java.lang.String).
|
That's exactly what I meant. I wrote a couple of name resolvers for my types (for instance, in my app we intern strings in a custom char array), so I need to see the resolved value. Sometimes this can be a long string, for instance for lists or maps.
Quote: |
If I select an object in (for example) a tree view, the inspector shows details of the object including its fields, under the "Attributes" tab. If the object is an array it shows the values of each element in the array, with its Java object type where applicable. The exception is where further resolution has occurred as above, when the type is not displayed.
|
Yes, the field view is nice, but in the pane above the field table it would be good to display the resolved value as well.
|
|
|
Re: View object values in a View [message #652238 is a reply to message #652189] |
Thu, 03 February 2011 10:12 |
Iulian Dragos Messages: 23 Registered: July 2009 |
Junior Member |
|
|
Andrew Johnson wrote on Wed, 02 February 2011 18:12 | You can copy the value (Context Menu on the object, copy, value)
and paste it into the notes view.
You can also copy a selection e.g. ctrl-C and paste it (that gives the table headings too).
You can save a value to disk - that for huge arrays that gives the full value rather than a value truncated at approximately 1024 characters.
|
Yes, that's what I do sometimes.
Quote: |
We could modify the inspector view - either another row in the top part of the split pane or another tab at the bottom. We don't want to clutter the screen too much more however.
|
I would go for another row, for completeness. I think it's important, and if you're worried about clutter you can remove the super class (that is usually easy to find) or the string 'no GC root', which could instead be turned into another visual indicator, like a special icon next to the object address.
Regardless, I think the view is a good idea because it can be closed, or placed anywhere. Is there an extension point for that? I'd be happy to contribute a prototype (I'm not familiar with the code base though)
thanks!
|
|
|
|
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04960 seconds