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.
NetBeans IDE 4.2 [200504101800] on jdk 1.5.0_03 When new watch is added, all existing watches are evaluated again. This can lead to performance problems (J2ME debugging or watches, that are evaluated long time)
I can reproduce it.
Also when a watch is deleted, the others are refreshed. This is because ModelEvent.TreeChanged is fired in WatchesTreeModel, which in turn calls rootNode.setObject (model.getRoot ()); in TreeModelRoot. We need an event like NodeChildrenChanged, which would refresh only the list of children and not node's properties.
More fine-grained firing is necessary - depends on issue #60499.
Fixed using a workaround for more fine-grained firing. Issue #60499 will address the API change that allows to fix it in a better way. /cvs/debuggercore/viewmodel/src/org/netbeans/modules/viewmodel/TreeModelNode.java,v <-- TreeModelNode.java new revision: 1.36; previous revision: 1.35 /cvs/debuggercore/viewmodel/src/org/netbeans/modules/viewmodel/TreeModelRoot.java,v <-- TreeModelRoot.java new revision: 1.12; previous revision: 1.11 /cvs/debuggercore/src/org/netbeans/modules/debugger/ui/models/WatchesTreeModel.java,v <-- WatchesTreeModel.java new revision: 1.5; previous revision: 1.4 /cvs/debuggerjpda/src/org/netbeans/modules/debugger/jpda/models/WatchesModel.java,v <-- WatchesModel.java new revision: 1.18; previous revision: 1.17
Verified on build 200510111800