The information in this article applies to:
SYMPTOMSWhen 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. CAUSEThe 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. RESOLUTIONIf 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. STATUSThis behavior is by design. MORE INFORMATIONApplications 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:
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:
Additional query words: 0Client drag/drop Word
Keywords : kbole kbMFC kbVC |
Last Reviewed: July 26, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |