Bug 76145 - [EditorMgmt] [RCP] Control where new Editors are opened in the workbook
Summary: [EditorMgmt] [RCP] Control where new Editors are opened in the workbook
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1   Edit
Hardware: All All
: P4 enhancement with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-10-13 03:54 EDT by Rene CLA
Modified: 2019-09-06 16:13 EDT (History)
2 users (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 Rene CLA 2004-10-13 03:54:43 EDT 
I'd like to control programmatically where new Editors are opened in the
Editorarea. By default each editor is tabbed behind the previous opened editor,
but I want that each new editor is opened beside the other editor. I want to see
the content of each editor at the same time. Manually after opening I can move
the Editors around to have this result, but I want to do this programmatically
after opening the editor.
The reason for this request is:  I have a RCP App which Editors that contain a
TableViewer. It is possible to Drag & Drop entries of the Table between the
Editors. So it would be really nice to open new Editors beside each other,
instead of tabbing them behind the previous opened.
Comment 1 Michael Van Meekeren CLA 2006-04-21 13:19:47 EDT 
Moving Dougs bugs
Comment 2 Susan McCourt CLA 2009-07-09 19:06:17 EDT 
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
Comment 3 Boris Bokowski CLA 2009-11-17 13:05:07 EST 
Remy is now responsible for watching the [EditorMgmt] component area.
Comment 4 Eclipse Webmaster CLA 2019-09-06 16:13:26 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.