Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 378537 - CommonNavigator to Open Project by double-click, like jdt
Summary: CommonNavigator to Open Project by double-click, like jdt
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: IDE (show other bugs)
Version: 4.2   Edit
Hardware: PC Windows 7
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-04 14:20 EDT by valentin Mising name CLA
Modified: 2019-11-27 07:41 EST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description valentin Mising name CLA 2012-05-04 14:20:34 EDT 
Build Identifier: Version: 3.8.0 Build id: I20120125-1800

Double-click invokes expand action but it does not work for closed projects. 
We should override the method

	protected void handleDoubleClick(DoubleClickEvent anEvent) {
		super.handleDoubleClick(anEvent); // this expands the nodes
		
		// open project 
		IActionBars ab = getViewSite().getActionBars();
		IAction op = ab.getGlobalActionHandler(IDEActionFactory.OPEN_PROJECT.getId());
		op.run();
	}

There are actually many things that must be migrated from jdt to platform
http://valjok.blogspot.com/2012/02/having-problem-marks-in-eclipse-editor.html
But, you can start with this one.

Reproducible: Always
Comment 1 Steffen Pingel CLA 2014-06-16 09:39:03 EDT 
*** Bug 437420 has been marked as a duplicate of this bug. ***
Comment 2 Lars Vogel CLA 2019-11-27 07:41:54 EST 
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.

If the bug is still relevant, please remove the stalebug whiteboard tag.