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.
Currently, each time you step, or between each subsequent breakpoint stop, all the nodes in the Local Variables collapse. This is frustrating, and ruins productivity, exaggerated when the variable in interest is many nodes deep. I wouldn't have thought it be hard to remember if a node was in open or closed stated, and to restore it. If these nodes are constructed new each time, then to keep some cache in the TopComponent of what the previous view (the names, or some universal identifier, of which nodes were open) was.
I can reproduce it.
No chance to fix it in 4.1.
This works in Watches in dev builds. It should be possible to fix it for Local Variables as well...
Fixed in trunk: /cvs/debuggercore/viewmodel/src/org/netbeans/spi/viewmodel/Models.java,v <-- Models.java new revision: 1.18; previous revision: 1.17 /cvs/debuggerjpda/src/org/netbeans/modules/debugger/jpda/models/AbstractVariable.java,v <-- AbstractVariable.java new revision: 1.29; previous revision: 1.28 /cvs/debuggerjpda/src/org/netbeans/modules/debugger/jpda/models/Local.java,v <-- Local.java new revision: 1.5; previous revision: 1.4 /cvs/debuggerjpda/src/org/netbeans/modules/debugger/jpda/models/LocalsTreeModel.java,v <-- LocalsTreeModel.java new revision: 1.28; previous revision: 1.27 /cvs/debuggerjpda/src/org/netbeans/modules/debugger/jpda/models/ObjectLocalVariable.java,v <-- ObjectLocalVariable.java new revision: 1.5; previous revision: 1.4
*** Issue 61051 has been marked as a duplicate of this issue. ***
verified or just very old