Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 187972

Summary: [DND] IDropActionDelegate needs to reflect operation (DND.DROP_COPY, DND.DROP_MOVE, DND.DROP_LINK)
Product: [Eclipse Project] Platform Reporter: Klaus Wenger <kjwenger>
Component: UIAssignee: Platform UI Triaged <platform-ui-triaged>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3 Keywords: helpwanted
Version: 3.3   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard: stalebug

Description Klaus Wenger CLA 2007-05-19 15:51:56 EDT
Interface/method org.eclipse.ui.part.IDropActionDelegate#run(Object, Object)used by extension point "org.eclipse.ui.dropActions" does not reflect operation (DND.DROP_COPY, DND.DROP_MOVE, DND.DROP_LINK) indicated by user (keys CTRL, SHFT) on drop target.

The drop action is application-specific and needed to able to identify whether an acceptable source should be moved/linked/copied into the target.
Comment 1 Klaus Wenger CLA 2007-05-19 15:55:05 EDT
Our feature/plug-in is in the application life-cycle framework (ALF) realm and allows to move/share/copy action-items/activities between their containers. When workspace containers are shared using our version control management (VCM), the remote action-items should be allowed to be dragged and dropped onto shared workspace containers for convenience and simplicity invoking the DnD operation on their remote peers.
Comment 2 Eric Moffatt CLA 2007-05-22 15:53:34 EDT
If the target view is 'known' (i.e. you wrote it...;-) you could try caching the value in the view and getting it from the 'target' object (presumably the view) during the callback. Not very satisfying but it might work for now.

We're far past API freeze for 3.3 so this will have to be deferred to 3.4. Note that I'm expecting to re-work a lot of the DnD stuff in 3.4 (starting with SWT's API) so I'll make sure that I include this in the scenarios...
Comment 3 Eclipse Genie CLA 2019-08-28 16:46:09 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.

--
The automated Eclipse Genie.