If you have LabVIEW 7.1, you can do the following.
Use an event structure to capture the keystroke you want to map to mouse down. When the event occurs, use the VIs in the Advanced->Input Device Control palette to query the mouse for its position. Use this position and a look-up table to fire a user event to effect the mouse press (e.g. push a button). You will probably be making heavy use of property nodes to do all this. Note that booleans cannot have
Mechanical Action equal to
Latch When Pressed or
Latch When Released if you use locals or property nodes to set their state. This will necessitate your code performing the initialization and latch code. This is easy with the event structure, but it is a “gotcha” you need to watch out for.
If you have LabVIEW 7.0 or earlier, you may need to call into a system shared library or use the picture control or some other method to get the mouse coordinates. You can search the net for possibilities -
here is one.
If you have LabVIEW 6.1 or earlier, you cannot use user events, so substitute a queue driven task handler for your “user events.” You may want to do that, anyway, as it efficiently separates your tasks from your events - something all easily-maintained GUIs do.
Finally, if you use LabVIEW 6.0 or earlier, you will need to poll for the keystroke event, since there is no event structure. About every 50ms should do it. You will get reasonable response without killing your CPU.
