Bug 273753 - [EditorMgmt] [DND] Enhancement: Create new editor by alt/option dragging editor tab
Summary: [EditorMgmt] [DND] Enhancement: Create new editor by alt/option dragging edit...
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: IDE (show other bugs)
Version: 3.5   Edit
Hardware: Macintosh Mac OS X
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-26 19:53 EDT by Jason Swartz CLA
Modified: 2019-09-06 16:04 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jason Swartz CLA 2009-04-26 19:53:04 EDT
Build ID: I20090407-1430

This is an enhancement request to allow users to create new editor windows for existing editor windows by alt-dragging the editor tab. This is a shortcut to the normal process of right clicking in an editor tab and selecting "New Editor".

Suggested Steps To Reproduce:
1. Open an editor
2. Hold down alt/option and drag the editor tab to a new location
Result: a new editor window will be created, and the original editor unchanged


More information:
Comment 1 Eric Moffatt CLA 2009-04-27 14:29:57 EDT
I'd use 'Ctrl' rather than 'Alt' since it's the Copy modifier for regular DnD operations...

If we go this route we may also want to allow the same gesture to create new instances of multi-instance views.
Comment 2 Mike Wilson CLA 2009-05-05 14:46:18 EDT
Changing Version tag to something more believable. Note that this is not a statement about when the enhancement request will be addressed (the Target Milestone field is used for that); the Version tag should be set to the version of Eclipse you were using when you saw the need for the enhancement.
Comment 3 Boris Bokowski CLA 2009-11-17 12:59:00 EST
Remy is now responsible for watching the [EditorMgmt] component area.
Comment 4 Eclipse Webmaster CLA 2019-09-06 16:04:35 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.