Bug 78388

Summary:	[DND] Editors opened with drag/drop should open in the stack they were dragged over
Product:	[Eclipse Project] Platform	Reporter:	Paul Smith <paul.smith>
Component:	UI	Assignee:	Platform UI Triaged <platform-ui-triaged>
Status:	ASSIGNED ---	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	christophe.cornu+eclipse, markus.kell.r
Version:	3.1
Target Milestone:	---
Hardware:	PC
OS:	Windows NT
Whiteboard:

Description Paul Smith

2004-11-11 09:57:16 EST

If you have two files open, split between two panes, then open a third by
dragging from Package Explorer or Navigator onto the second pane - the file is
opened in the first pane.

Follow this:
Open two files from Package Explorer.
Drag the one of the file editor tabs down so that it ends up in a new pane in
the bottom half of the editor (like a horizontal split).
Drag a third file from Package Explorer onto the lower pane and let go.
The file is placed in a tab on the top pane. Not what I want.

Comment 1 Kim Horne

2004-11-11 09:59:55 EST

Hrm.  I can't reproduce this exactly.  I'm finding that the editor is stacked in
the same folder as the currently active editor.

Comment 2 Paul Smith

2004-11-11 10:00:53 EST

I'm not sure what determines which pane the third file is openned in but it is
not necessarily the top one, as per my example.
If it does open in the bottom pane, then it will not open in the top pane if you
drag it from the package explorer.

Comment 3 Paul Smith

2004-11-11 10:06:43 EST

Kim, you're right. I see now.
Surely I should not have to make the pane 'active' ready to drag a new file into
though.

Comment 4 Stefan Xenos

2005-04-28 16:47:02 EDT

You're right that this could be improved. Right now the entire editor area is
one big drop target, but it would make sense to open editors in the stack they
were dragged over.

Comment 5 Markus Keller

2007-05-10 09:19:42 EDT

*** Bug 110096 has been marked as a duplicate of this bug. ***

Comment 6 Eclipse Webmaster

2019-09-06 16:13:44 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.