Community
Participate
Working Groups
Build 20020924 The menu item "Project->Open Project" activates either when the packages view is active or when a closed project is selected in the navigator view. Since this action just pops up a dialog displaying the currently closed packages, the menu item's activation should only be based on whether or not there are closed projects in the workspace.
Works properly for me.
This doesn't work in Build 20021114. 1. Close a project. 2. Close the packages view and navigator. 3. Click "Project". 4. The "Open Project" menu item is disabled despite the fact that there is a closed project in the workspace.
The problem is no part is providing an action handler for this global action. Nevetherless, this implementation problem is not intuitive for the user. Need to investigate what could be done here.
Just making the action be enabled always would be better than what we have today. The "best" solution would probably involve a listener that would update the action's enablement based on project open/close events, but this really seems like overkill. If the action is enabled all the time, the worst that will happen is a user who has no closed projects will click "Open Project" and see an empty dialog, informing them that they've got no closed projects.
Not for release 2.1
Doesn't work in 2.1. It is greyed out if you have any resource in an open project selected. If you deselect the current item (Ctrl click) then the menu item is now enabled. This should really be fixed to always allow a project to be opened if there is at least one project that is closed. It shouldn't behave differently depending on what is selected.
This is particularly problematic when you really like the Java Browsing Perspective. It's easy for something in the Project pane to be selected, which renders the Open Project action either hidden from popup menus, or grey out. Switching perspectives, or ctrl-clicking the currently selected node in projects pane makes the action available again. Hardly critical, but more of a usability PITA. Under what circumstances would you NOT want the Open Project action enabled?
This usability issue is still present in 3.0M3 (using Win2000). If anything at all is selected in the Projects View, there is no 'Open Project' option in the context menu, and the 'Open Project' option is greyed out in the drop-down Project menu. Also, there's no obvious way to make it so that nothing is selected in the view (for instance, by clicking on unoccupied 'white space'). After a few false starts, I found that I could get the desired effect by holding down CTRL and clicking on whatever items are selected to un-select them - damn fiddly!
This seriously has been annoying me for so long I am posting again. WHY is the Open Project disabled in the first place... Again, under _what_ condition should/would/could you not want to be able to open a project? At the momemt, this is the steps I have to take to open a project: * Open/Show the Package Explorer * CTRL+Click the currently selected item to unselect it * Now I can choose Open Project Doesn't that sound silly? If you have a number of projects, but not all open to minimise confusion, then to reopen one is a pain. Having said all that, 3.0 is grooooovy.
Is this still an issue in 3.2?
Yes. Please just enable the action.
Assigning to component owner PW
I want to note that the 'Open Project' action being exected when the active view is the 'Package Explorer' and the one that is executed when the active view is the 'Navigator' or the 'Project Explorer' is _not_ the same. There is the org.eclipse.jdt.ui.actions.OpenProjectAction from JDT and org.eclipse.ui.actions.OpenResourceAction that is from the Platform. JDT's will provide a listing of projects in a dialog whereas the Platform's only opens the projects that have been currently selected. Both does suffer from the deactivation behaviour described in this bug. While the Platform's one is called OpenResourceAction, it actually is coded to work with projects only. I propose that the action be changed to provide a listing like JDT's in a dialog and a separate bug be filed for JDT to enable/disable their action accordingly and/or just adapt the Platform's updated action once that's fixed.
Jared, are you fine if a listing of closed projects is provided like what happens now if you bring up the context menu on an opened project in the 'Package Explorer' and select 'Open Project' if no projects is currently selected? Paul, is it cool if we return false only if we currently have no closed projects in the workspace? I will proceed with writing a patch if both parties have no problems.
Yep. Allowing the user to choose from the list of closed projects makes sense.
> and a separate bug be filed for JDT to >enable/disable their action accordingly I've fixed that in HEAD for the Package Explorer.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
