On Jul 12, 2006, at 8:50 AM, Karen wrote:
I think if DropObject fires DragExit SHOULD not because the object being dragged never exits... after all it was dropped there!
However, if the control is drawing a custom accept-drop image, putting the code to remove that indicator in the DragExit event seems like a likely candidate. If the DragExit event didn't fire, you would need to put this code in two spots.
My understanding was that DragExist in the companion to DragEnter to track movement into and out of a given control, not to mark the end of the drag if dropped...
DropObject will always signal that something has been dropped. DragExit simply says that the drag is no longer within your control's bounds, which is true if the drag no longer exists.
And DragEnter/DragExit should not fire unless the control can accept that drop...
DragEnter should always fire. If you return true, you tell REALbasic that you want to handle the drag operation, regardless of whether or not your control registered to handle that type of drag. Similar to MouseDown/Drag/Up, DragOver and DragExit will not fire if you do not return true from DragEnter. The return value from DragOver tells REALbasic whether or not your control is accepting the drop.
I vaguely recall seeing inconstancies Xplatform in these behavior but I may be wrong.
If any inconsistencies are found, please do file bug reports. Thanks, Jon -- Jonathan Johnson [EMAIL PROTECTED] REAL Software, Inc. _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
