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

Bug 233740

Summary:	[DnD] Cannot drag and drop files from Windows Explorer when Eclipse is running elevated as Administrator on Vista
Product:	[Eclipse Project] Platform	Reporter:	Chris Chiu <chris.chiu>
Component:	SWT	Assignee:	Platform-SWT-Inbox <platform-swt-inbox>
Status:	CLOSED WONTFIX	QA Contact:	Kevin Barnes <cocoakevin>
Severity:	normal
Priority:	P3	CC:	contact, duongn, gheorghe, karsten.thoms, paul-eclipse
Version:	3.4	Keywords:	triaged
Target Milestone:	---
Hardware:	PC
OS:	Windows Vista
Whiteboard:	stalebug

Description Chris Chiu

2008-05-23 14:37:26 EDT

Build ID: I20080502-0100

Steps To Reproduce:
1. Login to Vista using an admin account.  Leave UAC enabled.
2. Create any text file on the desktop.
3. Locate eclipse.exe in Windows Explorer. Right click on eclipse.exe and select Run As Administrator. Click Allow to elevate when prompted by UAC.
4. Drag and drop the text file over to Eclipse editor area.  Note the cursor shows not allowed.

Repeat step 3 and 4 without elevation, DnD the text file onto Eclipse works as expected.

More information:
From various threads on the net, Explorer process is running with normal integrity level while Eclipse is running elevated. The Explorer process cannot send DnD messages to a higher integrity level process like Eclipse under Vista.

It seems possible to workaround the problem if Eclipse (SWT) registers itself to allow such messages via ChangeWindowMessageFilter API in Vista.

Comment 1 Leo Ufimtsev

2017-08-03 12:26:16 EDT

This is a one-off bulk update. (The last one in the triage migration).

Moving bugs from swt-triaged@eclipse to platform-swt-inbox@eclipse.org and adding "triaged" keyword as per new triage process:
https://wiki.eclipse.org/SWT/Devel/Triage

See Bug 518478 for details.

Tag for notification/mail filters:
@TriageBulkUpdate

Comment 2 Eclipse Genie

2019-10-07 15:05:08 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.

Comment 3 Karsten Thoms

2019-10-08 03:03:59 EDT

Closing since Vista is not supported. Feel free to reopen when this is still a problem with current OS & Eclipse versions.

Comment 4 Paul Pazderski

2019-10-08 03:14:32 EDT

It is the same with current Eclipse and Windows 7/10 but imo a sane and expectable behaviour. Won't fix is absolute fine for me.