Bug 116865

Summary: [EditorMgmt] Double click of a file does not use selected editor.
Product: [Eclipse Project] Platform Reporter: Kelly <rkwiles>
Component: UIAssignee: Platform UI Triaged <platform-ui-triaged>
Status: NEW --- QA Contact:
Severity: normal    
Priority: P3    
Version: 3.2   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:
Attachments:
Description Flags
pref file none

Description Kelly CLA 2005-11-17 08:47:52 EST
When I double click on a java file that has been assigned the designer editor
from Window Builder Pro by Instantiations, Eclipse does not open the file in the
Designer editor but uses the normal java editor.

I changed the default editor in the Preferences to the Designer editor but now
even non-GUI java files are opened with the Designer.

When I right click a file that should be opened in Designer it shows the
Designer editor as it's default editor.

This worked in 3.2M2

I am using versions

Eclipse SDK
Version: 3.2.0
Build id: I20051102-1600

WindowBuilder Pro
Version: 4.2.1
Build id: 2005.11.16

Java 1.5.0_05
Comment 1 Douglas Pollock CLA 2005-11-17 10:56:35 EST
Can you attach your 
"<workspace>/.metadata/.plugins/org.eclipse.core.runtime/.settings/org.eclipse.ui.workbench.prefs" 
file? 
 
Comment 2 Kelly CLA 2005-11-17 13:36:43 EST
Created attachment 30161 [details]
pref file
Comment 3 Michael Van Meekeren CLA 2006-04-21 13:19:03 EDT
Moving Dougs bugs
Comment 4 Susan McCourt CLA 2009-07-09 19:08:22 EDT
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
Comment 5 Boris Bokowski CLA 2009-11-17 13:04:39 EST
Remy is now responsible for watching the [EditorMgmt] component area.
Comment 6 Eclipse Webmaster CLA 2019-09-06 16:13:38 EDT
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.