Bug 35727

Summary:	[DND] StructuredViewer.addDragSupport should be setDragSupport
Product:	[Eclipse Project] Platform	Reporter:	Nick Edgar <n.a.edgar>
Component:	UI	Assignee:	Platform UI Triaged <platform-ui-triaged>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	Keywords:	api
Version:	2.1
Target Milestone:	---
Hardware:	PC
OS:	Windows 2000
Whiteboard:	stalebug

Description Nick Edgar

2003-03-26 15:26:52 EST

build I20030325

As of 2.1, SWT now enforces a limit of one DragSource per control.
See bug 35214 for details.

We should deprecate StructuredViewer.addDragSupport and change it to 
setDragSupport.

Comment 1 Randy Hudson

2003-05-28 21:35:39 EDT

What about changing to use addDragSupport(TransferDragSourceAdapter adapter)
and using the delegating drag source?

This probably isn't the best fix, since the client might use both the old and 
new api, and end up with two drag sources again.  But, at least it allows for 
multiple sources.

Comment 2 Eric Moffatt

2006-06-26 16:08:35 EDT

It's not that simple; the Delegating DropAdapter expects its world to be static (i.e. it needs to know everything up front). If we want to allow contributed drag sources and targets then we have to be OSGI compliant so we need a delegating adapter that is capable of updating the SWT 'singleton' as necessary (i.e. as new plugins are loaded/removed). Also, the delegating classes have to implement the correct 'lazy loading' strategies which involves making 'proxy' transfers that mask as the real one and then only load the plugin when necessary.

I have a version of this waiting on cycles to get back to it...

Comment 3 Eclipse Webmaster

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

Comment 4 Eclipse Genie

2021-10-20 17:02:20 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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.