Bug 124363 - [DnD] Enable Drop operation on the tab for editor
Summary: [DnD] Enable Drop operation on the tab for editor
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1.1   Edit
Hardware: PC Windows 2000
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-18 14:48 EST by Steve Gevers CLA
Modified: 2019-09-06 16:14 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Steve Gevers CLA 2006-01-18 14:48:30 EST
I have implemented a customized editor that operates on items in a database.  The editor contains Table (TableViewer) containing a list of associated items. I wanted to be able to move an associated item in one list to the list of another open editor.  I have created a custom Transfer type and instantiated a DragSource for the Table so that I can drag one of the items from the table.  I can't instatiate a DropTarget on the editor itself.  Although I could create a DropTarget for the list and have the editors opened side by side, I really didn't want the user to go through the hassle of having to drag the editors to get them opened side by side.  I hoped to be able drop the item on the tab for the target editor, and for the DropTargetListener to validate the drop and update the table.

Note that bug #37595 could be a solution as well.  If dragging and hovering over the desired editor were to make that editor active without cancelling the dnd, then I could drop the item on the table for the other editor.
Comment 1 Eric Moffatt CLA 2007-06-21 14:13:04 EDT
Yet another 'activate on hover' candidate...
Comment 2 Eclipse Webmaster CLA 2019-09-06 16:14:32 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.