PRB: OLE Drop Target Does Not Permit Drop

Last reviewed: February 18, 1998
Article ID: Q139648
The information in this article applies to:
  • The Microsoft Foundation Classes (MFC) included with:

        - Microsoft Visual C++ for Windows, versions 1.5, 1.51, 1.52, 1.52a
        - Microsoft Visual C++, 32-bit Edition, versions 2.0, 2.1, 2.2
    

SYMPTOMS

When you drag an OLE object over a given drop target window, the cursor feedback indicates that a drop is not allowed. However, the same object can be dropped on other drop targets successfully, and other objects can be dropped on the given drop target.

CAUSE

The object descriptor for the object indicates the size of the object is (0,0), and the drop target window's OnDragOver method is using the object rectangle to determine whether the object is within the client area of the window.

RESOLUTION

If the computed position rectangle for a data object is empty, inflate the rectangle to size (1,1) before testing whether the rectangle is within the client area of the drop target window.

STATUS

This behavior is by design.

MORE INFORMATION

Applications that register a window as an OLE drop target should probably check the position of a data object that is dragged over the window before permitting a drop to occur. For example, the MFC sample program Oclient performs the following check in its OnDragOver method:

   DROPEFFECT CMainView::OnDragOver(COleDataObject*,
      DWORD grfKeyState, CPoint point)
   {
      // adjust target rect by original cursor offset
      point -= m_dragOffset;
   
      // check for point outside logical area (in hatched region)
      // GetTotalSize() returns the size passed to SetScrollSizes
      CRect rectScroll(CPoint(0, 0), GetTotalSize());
   
      CRect rectItem(point,m_dragSize);
      rectItem.OffsetRect(GetDeviceScrollPosition());
   
      DROPEFFECT de = DROPEFFECT_NONE;
      CRect rectTemp;
      if (rectTemp.IntersectRect(rectScroll, rectItem))
      {
         //... figure out the drop effect
      }
   
      //...update drop effect
   
      return de;
   }

However, for some objects, such as Microsoft Word version 6.0 Documents, the m_dragSize reported by the data object is (0,0). In this case, the call to IntersectRect returns FALSE, and the drop effect returned is DROPEFFECT_NONE.

When the object position rectangle is inflated to size (1,1), IntersectRect returns TRUE and the correct drop effect is returned. In the previous example, you would inflate the rectangle by adding the following lines after the rectItem is declared:

   if (rectItem.IsRectEmpty())
   {
      // Some applications might have a null size in the object descriptor
      rectItem.InflateRect(1,1);
   }


Additional query words: 0Client drag/drop Word
Keywords : MfcOLE
Technology : kbMfc kbole
Version : WINDOWS:1.5,1.51,1.52,1.52a;Winnet:2.0,2.1,2.2
Platform : NT WINDOWS
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: February 18, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.