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.
In NB 3.5.1, select sampledir root, press Ctrl-N, choose Folder, type "foo/bar/baz", Finish. "foo" and "bar" folders are expanded, "baz" folder is selected, all is well. In a dev build, I try the same. First, "foo" is not expanded or selected - maybe a bug, but OK. However when I move the selection with the KB to "foo" and press Right to expand it, nothing happens. If I click on the expand handle once, nothing happens; clicking again expands it (and "bar" too), showing "baz". After that, it responds normally.
It have to be investigated what's wrong and fixed in 3.6, I add a label STARTED to don't be left in 3.6.
Can you reproduce it too?
Yes, I can, it's pretty easy. I'm going to increase the priority if needed.
Evaluation: JTree supposes a node is expanded => does not expand node (because is "expanded"). If you collapse node and expand again it works. A problem is in TreeView.treeExpanded where post and cancel RP task.
Assigned to new owner.
Observed in 040722 (1.5.0 b58) in Files tab.
Another issue which I think is the same: 041011 custom, JDK 1.5.0. Had nbbuild/javadoctools/apichanges.xsl open in the editor. Pressed C-S-3. Favorites tab has nb_all as a favorite dir, but nothing was expanded. If I click on the expand handle for nb_all, nothing happens. Click again and it expands - now showing the full path to apichanges.xsl (and now C-S-3 works).
Reproduced in latest dev. Reproducible only when invoking "New" on top-level node (e.g. project node in the Files view), never on the src node.
In fact, it is random, but likely enough to reproduce. The problem is timing, sometimes the expand request comes before visualizers manage to notify the addition.
openide/src/org/openide/explorer/view/TreeView.java,v1.175 openide/src/org/openide/explorer/view/VisualizerNode.java,v1.45
*** Issue 48613 has been marked as a duplicate of this issue. ***
this bug seems to be out of date, no such problem in 4.2 latest dev, verifying