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.
[ JDK VERSION : 1.7.0_45 ] STEPS: 1) Mark project node in Project Browser, no files open in editor pane. 2) Close NetBeans IDE. 3) Start NetBeans IDE. 4) Click menu Team. 5) Close Start Page. 6) Click menu Team. ACTUAL: 4) Project related sub menus are presented. 6) Default sub menus are presented, even while project is still selected. EXPECTED: 6) Project related sub menus should be presented when project is selected.
then probably the project is not selected. Make sure you focus the projects view and select the project node between 5) and 6)
(In reply to Ondrej Vrabec from comment #1) > then probably the project is not selected. Make sure you focus the projects > view and select the project node between 5) and 6) How can user know if project is selected? If the project node is coloured, the project looks selected for the user. IMO, closing a editor pane, here Start Page, should not deselect the before selected project silently, or at least the project node should become uncoloured. OK, this is only a little nit, but maybe simple to correct.
it is still selected but maybe the projects view itself is not focused so in global context another node is active. When you close the start page do up+down arrows work immediately in the projects view (without clicking into the projects view, does the selection change)?
I think, there is also another inconsistency. If I click in the empty navigator window, the project selection gets lost, but not if I click in the empty editor window. Contrary, if I click in the not-empty output window, where the open mercurial status tab is referring to this project, the project stays unselected, which user does not expect.
(In reply to Ondrej Vrabec from comment #3) Ok, there seem to be 2 levels of project selection, global and view-wise. The rule seems to be, that the project selection is only active (notified in the main window title), if there is a sub-object of the project selected in the respective view. But this rule seems not to be implemented consistently, as you can see from comment 1. My expectation is, if a project selection is active and if a closing of a neutral object in another view leads to an empty view, the active project selection should fall back to the before state.