PRB: Shell Returns DROPEFFECT_NONE Instead of DROPEFFECT_MOVE

Last reviewed: March 10, 1998
Article ID: Q182219

The information in this article applies to:

Microsoft Win32 Software Development Kit (SDK)
Microsoft Windows NT 4.0

SYMPTOMS

When a file is moved onto a shell window in Windows NT 4.0 through OLE Drag- and-Drop and the CF_HDROP format, DoDragDrop returns DROPEFFECT_NONE instead of DROPEFFECT_MOVE, even though the file is successfully moved.

CAUSE

The Windows NT 4.0 shell optimizes the move operation by moving the file itself. A return value of DROPEFFECT_MOVE tells the calling program that it should delete the file itself. However, since the shell has already done this, it returns DROPEFFECT_NONE.

RESOLUTION

If the originating program needs to know if the file actually was moved, it can check to see if the source file still exists.

Windows 95 also performs this optimized move, but returns DROPEFFECT_MOVE.

STATUS

This behavior is by design.

Keywords          : KBShell ShlDND
Version           : WINNT:4.0
Platform          : winnt
Issue type        : kbprb

================================================================================

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: March 10, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.