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

Bug 335245

Summary: DND Image exists as a child in the window of the drag source
Product: [Eclipse Project] Platform Reporter: Juan Narvaez <juan.narvaez>
Component: SWTAssignee: Platform-SWT-Inbox <platform-swt-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: eclipse.felipe, juan.narvaez
Version: 3.6.1   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard: stalebug
Attachments:
Description Flags
patch (not finished) none

Description Juan Narvaez CLA 2011-01-24 16:01:47 EST 
Build Identifier: 3.6.0.v3650b

When setting an image on a DragSourceEvent the resulting window that is created is a child of the window of the DragSource. The image only shows up when the drag operation is within that window and the image is not shown when dragging from window to window or from one application to another.

Reproducible: Always

Steps to Reproduce:
1. Create a drag source
2. Add a drag listener
3. Set an image within that drag listener when the on dragStart
4. Drag outside of the window
Comment 1 Felipe Heidrich CLA 2011-01-25 16:40:59 EST 
Yes, this is a limitation of the current implemetation.
To fix that we would have to re implemented our drag source and drop target to use IDragSourceHelper, IDropTargetHelper.
At some point I wrote this code but it was never released (we were afraid the code would have a memory leak in the IDataObject that I wrote for it). I'm trying to find the code to attach to the PR.
Comment 2 Felipe Heidrich CLA 2011-01-27 15:29:39 EST 
Created attachment 187772 [details]
patch (not finished)

The patch is in a development state and still has severals hacks. I'll post it here anyway so that the code doesn't get lost.
Comment 3 Felipe Heidrich CLA 2011-01-27 15:33:22 EST 
as far as i remember, this patch was developed to fix problems such as Bug 280158 and Bug 130037.
Comment 4 Lars Vogel CLA 2019-09-24 13:51:25 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.