02-13-2009, 01:43 PM
Hi Gintaras,
I have used QM to interface with one application that supports a Tcl scripting interface. I have used QM to control the application through sending keyboard mapped controls (i.e. QM monitors for triggers and then sends keyboard commands to the app display window which I have mapped internally in the application to perform various actions) and scraping onscreen elements.
The question I have is whether there is a better way to pass information and triggers from one scripting system to the other.
Currently if I want the Tcl script to trigger a macro/function in QM, I write a variables contents to a file which QM is monitoring for any modifications...
e.g.
Function UpdateInfoBox
Trigger $f 0x48 "$system$" "Tcl Output File.txt"
Is there a better in/out mechanism than this? This works ok but sometimes the file is not available or gets locked by the application.
Thanks,
Stuart
I have used QM to interface with one application that supports a Tcl scripting interface. I have used QM to control the application through sending keyboard mapped controls (i.e. QM monitors for triggers and then sends keyboard commands to the app display window which I have mapped internally in the application to perform various actions) and scraping onscreen elements.
The question I have is whether there is a better way to pass information and triggers from one scripting system to the other.
Currently if I want the Tcl script to trigger a macro/function in QM, I write a variables contents to a file which QM is monitoring for any modifications...
e.g.
Function UpdateInfoBox
Trigger $f 0x48 "$system$" "Tcl Output File.txt"
Is there a better in/out mechanism than this? This works ok but sometimes the file is not available or gets locked by the application.
Thanks,
Stuart