>Hi Hilmar,
>
>I just noticed that the MOUSE AT command supports the ability to specify a form/window to be clicked on so one just needs to know to the mouse coordinates relative to the current _Screen, toplevel form, toplevel child form, or tooblar. As you pointed out, OBJTOCLIENT is sufficient for determining coordinates relative to a control's parent form container.
OK, glad it works.
But, looking back at your message, I am thinking the following: I never saw the need to use the MOUSE command, especially since the existence of VFP. For example, to activate a CommandButton, you can invoke
ThisForm.CmdStart.Click(), and for a TextBox, you can put the cursor into it with
.SetFocus(), and even change the cursor position with the
.SelStart property.
In summary, perhaps other alternatives are better than the MOUSE command.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
