Summary: | Resources opened in wrong editor when changing the default | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Randy Hudson <hudsonr> |
Component: | UI | Assignee: | Eduardo Pereira <eduardo_pereira> |
Status: | VERIFIED FIXED | QA Contact: | |
Severity: | major | ||
Priority: | P2 | ||
Version: | 2.0 | ||
Target Milestone: | 2.0.1 | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: |
Description
Randy Hudson
2002-07-11 10:24:18 EDT
Fix is in EditorManager "public IEditorReference openEditor(String editorId,IEditorInput input,boolean setVisible) throws PartInitException". Released in 201 stream. Fix released in both streams (201 and HEAD) Randy, are you saying that you don't close the .java files that you opened in the (default) Java editor, switch the default editor to Text Editor and then open the (still open) java files again? Or are you closing the java files and then reopen them when the Text Editor is the default editor. I'm trying to verify that this is fixed and don't even see your problem (unless it's the former scenario, which I doubt). In the latter scenario the Java files are opened in the standard text editor like I would expect. I'm trying this on R2.0. Is that where you originally had the problem? Is it fixed for you now in a more recent build? I believe I was using F3, but I can reproduce the following in 2.0 final. Right click on plugin.xml and manually chose the editor which is marked as the default, the PDE one. Change plugin.xml default editor to Text Editor. double click on the same plugin.xml, and the PDE editor opens. It is strange that in the initial step, double-clicking to open PDE's editor and manually opening PDE's editor results in something different later on. IMO, if I manually select the default editor for a resource, workbench should throw away the last used editor, not remember it. I'm not sure if F3 was different. I think I opened this bug in reference to plugin.xml, and there is a good chance that I had opened all of my plugin.xml files using the popup menu at that time. Reproduced on R2.0. Verified fixed in 20020821 (2.0.1) |