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.
[release32 apr 6] This is fairly annoying. I am in MDI mode, using the Editor. Explorer is showing something unrelated. Say I wish to see the compiler type for the current file. I Page Up to top of file, so selected node is JavaNode, and property sheet correctly shows the Properties and Execution tabs for this file. Now I go to click on e.g. the Execution tab--and this works, but immediately afterwards the property sheet switches to show properties of whatever is selected in the Explorer! The only way to get the properties for the file is to look it up in the Explorer and select it there. This does not happen in SDI mode--clicking on the Prop Sheet focusses that window, which has no node selection, so no problem. In MDI, apparently, when Prop Sheet is docked into Explorer - South, clicking on it gives focus to the whole Explorer + Prop Sheet pane, which incorrectly changes the node selection to whatever exists in the Explorer.
Target milestone -> 3.3
Still true in current dev builds.
*** Issue 15107 has been marked as a duplicate of this issue. ***
updating subcomponent to window system
Observation: 1. Undock Properties window from Explorer -> works correct 2. then dock Properties again to Explorer -> works correct
[Nov 13 dev] The synchronaztion Explorer panel and docked properties (the root of this issue) is valid until the properties undocked then it docked back.
solving issue 18010 will help this one, although I think it will not fix it completely.
Target milestone -> 3.3.1.
We discovered together with David Strupl that problem is wider, not only with property sheet, but with all top components which are "empty", means that they don't contain any specific buttons, text areas and so on. Roo problem is that these "empty" top components seems to not accept focus and don't receive focus_gained events. Will investigate it further...
After all, it seems that this issue can be fixed only in property sheet itself. Winsys rely on focus event messages when activating components in splitted frame type. So property sheet should react to mouse click and request focus for itself to be properly activated.All other components like editor, explorer do this (call requestFocus when mouse click arrives). I'm attaching patch which adds functionality for empty panel (used when no properties are shown). Please add the same support for panel which shows properties.
Created attachment 3654 [details] added support for EmptyPanel
Attaching thread dump from where the nodes get changed: at java.lang.Thread.dumpStack(Thread.java:1069) atorg.openide.explorer.propertysheet.PropertySheet.setNodes(PropertySheet.java:248) atorg.netbeans.core.NbNodeOperation$Sheet.setNodesWithoutReattaching(NbNodeOperation.java:401) atorg.netbeans.core.NbNodeOperation$Sheet.setNodes(NbNodeOperation.java:392) atorg.netbeans.core.NbNodeOperation$Sheet$Listener.activate(NbNodeOperation.java:557) atorg.netbeans.core.NbNodeOperation$Sheet$Listener.propertyChange(NbNodeOperation.java:542) atorg.openide.util.WeakListener$PropertyChange.propertyChange(WeakListener.java:325) atjava.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:255) atorg.netbeans.core.windows.RegistryImpl.tryFireChanges(RegistryImpl.java:314) atorg.netbeans.core.windows.RegistryImpl.selectedNodesChanged(RegistryImpl.java:270) atorg.netbeans.core.windows.frames.DefaultContainerImpl.doActivateComponent(DefaultContainerImpl.java:561) atorg.netbeans.core.windows.frames.DefaultContainerImpl.reactivateSelectedComponent(DefaultContainerImpl.java:726) atorg.netbeans.core.windows.frames.DefaultContainerImpl$2.run(DefaultContainerImpl.java:885) atorg.netbeans.core.windows.frames.DefaultContainerImpl$4.run(DefaultContainerImpl.java:900) at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:181) at java.awt.EventQueue.dispatchEvent(EventQueue.java:446) atjava.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:193) atjava.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:147) atjava.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:141) atjava.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:133) at java.awt.EventDispatchThread.run(EventDispatchThread.java:101)
*** Issue 20314 has been marked as a duplicate of this issue. ***
Raising, this is annoying.
*** Issue 21238 has been marked as a duplicate of this issue. ***
please also see User: ttran Date: 02/04/05 04:50:37 Modified: src/org/openide/explorer/view ListView.java TreeView.java Log: #20887: right-click on Node in Explorer tree doesn't show popup menu. #12520: TopComponent.getActivatedNodes() returns wrong nodes for context menu actions. The old fix for #12520 caused #20887. See comments in TreeView.java for details. Revision Changes Path 1.51 +3 -1 openide/src/org/openide/explorer/view/ListView.java http://openide.netbeans.org/source/browse/openide/src/org/openide/explorer/view/ListView.java.diff?r1=1.50&r2=1.51 1.83 +57 -34 openide/src/org/openide/explorer/view/TreeView.java http://openide.netbeans.org/source/browse/openide/src/org/openide/explorer/view/TreeView.java.diff?r1=1.82&r2=1.83
I don't think Dafe's suggested solution is the good one, mostly because the problem is not limited to global property sheet. It can be any TopComponent which falls into a similar situation as our global prop sheet. There are two other possible solutions (IMO better :-) - glass pane on top of every TopComponent - AWTEventListener I am going to fix this bug using the latter.
fixed in cvs trunk for NB 3.4 User: ttran Date: 02/04/09 03:33:22 Modified: src/org/netbeans/core/windows/frames SplitContainerImpl.java Log: #11149: [MDI] Click on property sheet, and Explorer gets focus. The fix is hacky. See comments in the code for details. Revision Changes Path 1.44 +73 -13 core/src/org/netbeans/core/windows/frames/SplitContainerImpl.java http://core.netbeans.org/source/browse/core/src/org/netbeans/core/windows/frames/SplitContainerImpl.java.diff?r1=1.43&r2=1.44
Seems it is working now.
Resolved for 3.4.x or earlier, no new info since then -> closing.