Bugzilla – Full Text Bug Listing
| Summary: | allow to drag attachments out of the attachments section | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Eugene Kuleshov <ekuleshov> | ||||||
| Component: | Mylyn | Assignee: | Project Inbox <mylyn-triaged> | ||||||
| Status: | CLOSED MOVED | QA Contact: | |||||||
| Severity: | enhancement | ||||||||
| Priority: | P4 | CC: | mik.kersten, steffen.pingel, tomasz.zarna | ||||||
| Version: | unspecified | Keywords: | helpwanted | ||||||
| Target Milestone: | --- | ||||||||
| Hardware: | All | ||||||||
| OS: | All | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
|
Description
Eugene Kuleshov
*** Bug 278924 has been marked as a duplicate of this bug. *** Created attachment 145204 [details]
non-working patch
Created attachment 145205 [details]
mylyn/context/zip
Unfortunately there is no straight forward solution to this problem: The drag source has to set the data on the DragSourceEvent before the drag is executed. The actual transfer is handled by the drop target. None of the SWT transfer types support remote resources though and copying attachments to the local file system during a drag is not an option since it would block the UI thread and drag operation. We may be able to make this work for LocalSelectionTransfers and some sort of implementation of IResource that does not actually correspond to a local resource but I haven't looked into that any further. Mylyn has been restructured, and our issue tracking has moved to GitHub [1]. We are closing ~14K Bugzilla issues to give the new team a fresh start. If you feel that this issue is still relevant, please create a new one on GitHub. [1] https://github.com/orgs/eclipse-mylyn |