Has anyone noticed that VFP's automatic OLE drag mode tends to kick in too quickly? This occurs whether I set OLEDragMode = 1 (Automatic), or if I use OLEDrag(.T.), which is only supposed to initiate the drag "after the user has pressed the mouse button for a sufficient period of time to indicate that a drag operation is occurring, or the mouse is moved a sufficient distance while the mouse button is pressed". Is there any way to adjust the parameters that govern this, e.g. via some registry settings?

The over-eagerness to start OLE drag mode really becomes a pain with controls that support other mouse behaviors like a right-click context menu or a double-click action. Even with a rock-steady hand, I find it extremely difficult to simply right-click or double-click without inadvertently going into an OLE drag. There seems to be no such trouble with non-VFP based controls like Windows Explorer icons, various ActiveX controls, and other Windows applications.

Incidentally, the behavior of VFP's own text editor clearly exhibits this problem. (God help you if you dare to select + right-click-and-drag in the VFP editor!) I can endure this annoyance as a developer, but I'd prefer not impose it on the users of my applications. Must I forego all use of automatic OLE drag detection and painstakingly attempt to fake up the effect that OLEDragMode = 1 was supposed to provide? What is the best solution?

TIA for any advice.

Mike