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.
| Summary: | [TTV] expands nodes when it shouldn't | ||
|---|---|---|---|
| Product: | platform | Reporter: | Torbjorn Norbye <tor> |
| Component: | Outline&TreeTable | Assignee: | Stanislav Aubrecht <saubrecht> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | blocker | ||
| Priority: | P3 | ||
| Version: | 3.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | DEFECT | Exception Reporter: | |
| Bug Depends on: | |||
| Bug Blocks: | 33281 | ||
Tor, I fixed the issue 29551 in TreeTable. The issue also describes bad behavior of a tree after node deletion. I think it might be same problem as in this issue. Could you try if the fix solves it? Thanks I think I'm still seeing an issue (because I'm typically replacing the entire node tree when this is occurring). Let me double check that and get back to you. Is it heavy asked for 3.5 or could be solve later? tor, any update on reproducibility of this issue? (it's pretty old one:) *** Issue 29724 has been marked as a duplicate of this issue. *** works for me - pls reopen this issue if you can still reproduce it |
I had this problem in the tasklist module that collapsed node trees would sometimes reexpand when other parts of the node tree were updated. This makes it really hard to use - you want to look at a later part in the tree, but the top part (which you had collapsed) keeps expanding and hiding I've tracked it down and believe the problem is in TreeTable.java, specifically org.openide.explorer.view.TreeTable$1.treeNodesRemoved(TreeTable.java:426) protected TreeModelListener createTreeModelListener() { return new JTree.TreeModelHandler() { public void treeNodesRemoved(TreeModelEvent e) { tree.setSelectionPath (TreeView.findSiblingTreePath (e.getTreePath (), e.getChildIndices ())); } }; } Note that the above code is called for ALL deleted nodes that are visible - not when the selected node is deleted. Note also that setSelectionPath is documented to expand nodes as necessary. So, after doing some document deletions, findSibling goes into a neighbor tree and expands it. I think the above code is an attempt to select the "next" element when the node that is selected is deleted - but that doesn't currently happen - so the above code doesn't achieve that. What it -does- however achieve is to expand collapsed nodes, something the user does not want. I commented out this code, and things work much better in the tasklist module. Are there any scenarios in netbeans the above is serving - if so, what are they? If not, can I request that the above is removed?