For single left mouse clicks specifically, you want WM_LBUTTONDOWN and WM_LBUTTONUP--posted/sent separately. For LBUTTONDOWN: WParam is a sum of MK_* bit flags that indicate if control, shift, other mouse buttons, etc. are down for the post; LParam is a long of x/y cursor coordinates, relative to the top-left corner of the window to which you'll post the message. I think you can post LBUTTONUP to the same window with 0s for w/lparam. The MSDN has decent entries on the messages and all the mouse messages themselves are in winuser.h. Also, I believe Doug Lee has written a "winclick" module (available at least as part of BX) that abstracts this into functions. On 10/16/2014 10:07 PM, Jim Snowbarger wrote: > Hey guys, > I have this script that is doing things in response to key combinations like > control+LeftArrow. Part of the processing for that was to do a left mouse > click at a location. But, since the control key is still down when the > script runs, it is also down when jaws does the leftMouseButton call. > Problem is that the application is sometimes getting a control left click, > instead of a straight left click. > If I wait for the control key to be released first, the interface is clunky, > but the problem goes away. > Is there a better way to send a mouse click to that window that might > obviate the confusion? > I'm thinkin of a SendMessage or PostMessage call. But, I don't know where > to find what message to send. > Thanks heaps for any help you can give. > > > __________� > > View the list's information and change your settings at > http://www.freelists.org/list/jawsscripts > __________� View the list's information and change your settings at http://www.freelists.org/list/jawsscripts