Bug 74724

Summary:	[DND] EditorAreaDropAdapter should ignore non-existing resources should be disabled
Product:	[Eclipse Project] Platform	Reporter:	Jean-Michel Lemieux <jean-michel_lemieux>
Component:	UI	Assignee:	Platform UI Triaged <platform-ui-triaged>
Status:	ASSIGNED ---	QA Contact:
Severity:	normal
Priority:	P3	CC:	duongn
Version:	3.0	Keywords:	helpwanted
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Jean-Michel Lemieux

2004-09-22 16:31:48 EDT

Currently you can drag incoming additions into the editor area and a blank
editor is opened instead of the remote. We should disallow this case.

Comment 1 Jean-Michel Lemieux

2004-09-22 16:32:05 EDT

consider for M2

Comment 2 Jean-Michel Lemieux

2004-09-23 10:41:12 EDT

3.0
When you drag non-existing resource into the resource navigator dropping is
disabled. However, when dropping into the editor area it is enabled. This seems
inconsistent. Also, when a non-existing resource is dragged into the editor area
a new file buffer is created, then when saved, doesn't show up as a resource in
the navigator.

To reproduce, generate an incoming addition in the synchronize view, then drag
that element around.

We don't want to disable dragging on non-existing resources from the sync view
because several of our views accept that case.

Comment 3 Eric Moffatt

2007-11-14 15:39:59 EST

Comitted in >20071114. No longer attempt to open the file but we still show the drop affordance. Duong, when I'm handling the 'dragEnter'/'dragOver' events the event.data field is null; is there any way to get the data in either of these methods?

Comment 4 Duong Nguyen

2007-11-14 17:14:25 EST

On some platforms (eg. Windows) the data is null until a drop occurs. The Windows implementation prevents data from being copied by the source prematurely.

Comment 5 Eclipse Webmaster

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