Bug 64147 - [EditorMgmt] Confusing UI indicator and editor behavior for opening a file with a different editor
Summary: [EditorMgmt] Confusing UI indicator and editor behavior for opening a file ...
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.0   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-05-26 11:45 EDT by May Zhu CLA
Modified: 2019-09-06 16:09 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description May Zhu CLA 2004-05-26 11:45:28 EDT
When a file is opened in an editor, a user tries to open it with a different 
editor. The UI indicator "." beside the editor switches to indicate the editor 
that the user attempts to open the file with, however the file is still open 
with the previous editor. Three issues contribute to this problem:
1. UI framework: the framework only allows a file to be opened once in one 
editor. The file has to be closed first to respond to an attempt of opening it 
with another editor. 
2. Usability issue: If sticks to this framework, a message should be popped up 
to remind user of closing the current opening file before she/he tries to open 
it with another editor.
3. BUG: UI indicator used to indicate which editor is open currently should be 
consistent with the actual opening editor.
Comment 1 Michael Van Meekeren CLA 2006-04-21 13:19:01 EDT
Moving Dougs bugs
Comment 2 Susan McCourt CLA 2009-07-09 19:05:03 EDT
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
Comment 3 Boris Bokowski CLA 2009-11-17 13:04:33 EST
Remy is now responsible for watching the [EditorMgmt] component area.
Comment 4 Eclipse Webmaster CLA 2019-09-06 16:09:41 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.