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.
There was a functionality of filtering out variables according to their access modifiers (public, private, protected). This functionality has disapeared with new window system. Is there going to be any replacement?
I need at least a simple UI spec.
*** Issue 37687 has been marked as a duplicate of this issue. ***
I have decided to remove this functionality. 1) Its not compatible with new WindowSystem. 2) Its useless. 3) It takes too much space on the screen.
Well, I appreciate your effort to lower number of issues. But I want clear statement from UI/HIE guys. Jano, please could you shed some light into this, thanks.
Jan, See issue #37687. We also need some of the other filters back like "super" which I find very useful.
I would like to clarify my comment. I was not correct when I wrote that its my decision to remove Variable Filters Toolbar. This toolbar was removed as a side effect of a new Window System by window core team. This change is defined in WS UI spec: http://ui.netbeans.org/docs/ui/ws/ws_spec-netbeans_ide.html Old code is not applicable for the new situation. So from my (debugger) point of view the replacement for filterring functionality is something like new feature. We do not know how to replace this functionality in the new window system, we do not have UI spec, we are late in development cycle. So, I have decided to not produce any replacement for this functionality to the nb3.6 release (at least).
Gili, can you describe me, how do you use "super" filter, and why do you need it? I am author of this toolbar, but I have never use it during a long time this toolbar is in netBeans. I think that its useless:) even its my "baby". Hanz
We need a new UI spec (feature specs) for features from old filter toolbar in case we want those features back. Else close this issue as won't fix.
My evaluation: - filtering of private, public and protected fields doesn't make much sense during debugging, as imprtance of field's value during debugging is not imposed by its access modifier. - "super" filter might be nice in some cases, especially if the class and its superclasses do not have many fields. Overall, this feature seems like a nice to have feature. Due to the resource constraint and not clear solution (how this feature should look like and where it should be placed) I suggest to postpone the resolution of this issue to a future release.
I am decreasing priority - P3 seems more appropriate.
*** Issue 40478 has been marked as a duplicate of this issue. ***
We should mention in the 3.6 release notes that we dropped this feature.
OK. I'll simply say that the feature has been deleted. It seems that there is no workaround, but it looks like people wouldn't care much anyway.
Well, Gili Tzabari and Ian Sullivan are at least two known guys requiring this feature back.
Perhaps I'm not a "known guy" but I work with NetBeans every day, and I use this feature. I'm somewhat baffled when I read some of the comments above, and what takes "too much space on the screen" is not the removed functionality, but all static and private fields in debug window. Try for example to watch the content of a Map which has Integer keys, or to debug Swing components which have hundreds of static/private/protected fields in a complex hierarchy of super-classes. (Not to mention the fact that debug window is now horizontal by default, so you can watch only 6 or 7 fields.)
Static filter has been replaced by "static" subnode. Inherited filter has been replaced by "Inherited" subnode of fields. Field node contains non-static, non-inherited fields only. Public/Private/Protected filters does not have any replacements, but they does not have a big sense during debugging. I think that all major usecases are covered now. So, I think that issue is fixed.
OK, verified.