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 206990 - Inherited fields together with non-inherited ones
Summary: Inherited fields together with non-inherited ones
Status: NEW
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 7.1
Hardware: All All
: P3 normal with 1 vote (vote)
Assignee: Martin Entlicher
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-06 15:44 UTC by fsttesla
Modified: 2012-10-07 17:09 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description fsttesla 2012-01-06 15:44:29 UTC
In the debugger's Variables window, it would be nice if the inherited fields were shown together with the non-inherited ones, without the need of expanding the Inherited node.
To avoid a too lengthy variables list, maybe the user could choose, for each class, a superclass as upper bound that establishes which inherited fields are to be shown immediately (with the non-inherited ones) and which ones are to be grouped (in the Inherited node). If such superclass is not set, the default behavior could be the current one.

I suggest this enhancement because relevant inherited fields often need to be sought in the Inherited node, but expanding a new node is quite annoying, especially if the variables tree is complex.
The second part of the idea could be added as new category in the Java debugger options (i.e. like Formatters and Step Filters). In fact it happens that, if there is some important inherited field, most times it isn't declared many classes up in the class hierarchy.
For example, assume MyButton extends JButton and I'm interested in viewing directly the fields up to AbstractButton. Then I could set AbstractButton as upper bound for MyButton, so that all non relevant fields from JComponent to Object are in the collapsed node.

Apart from this, sometimes the Static fields are useless. It would also be nice to have the possibility of hiding their node completely, maybe with a button in the Variables window left sidebar.
Comment 1 markiewb 2012-10-07 17:09:40 UTC
There should be an option (in the options dialog OR in the context menu OR as the toolbar item of the variables view) to disable the grouping of "inherited" and "static" variables.