02-08-2003, 10:56 AM
Command but simply sends BM_CLICK message to button window, but some programs requires real input. Possible variants:
lef 0.5 0.5 id(8 "Select Client")
lef 0.5 0.5 child("&ButtonText" "ButtonClass" "Select Client")
act id(8 "Select Client"); key V
Functions id and child will not find button if it is not standard Windows control (window), eg buttons in web pages or MS Office forms. When mouse pointer is over true button window, QM status bar usually displays "+Button" class name, but if it displays eg "+Internet Explorer_Server" or "+OForm" or "+F3 Server 60000000", and it does not changes when mouse pointer leaves button, then button is not true window, and QM will not find it. In future I will work to break this limitation.
I have no ideas about why key T does not work with that window. If you can use Tab manually, then key T also must work.
lef 0.5 0.5 id(8 "Select Client")
lef 0.5 0.5 child("&ButtonText" "ButtonClass" "Select Client")
act id(8 "Select Client"); key V
Functions id and child will not find button if it is not standard Windows control (window), eg buttons in web pages or MS Office forms. When mouse pointer is over true button window, QM status bar usually displays "+Button" class name, but if it displays eg "+Internet Explorer_Server" or "+OForm" or "+F3 Server 60000000", and it does not changes when mouse pointer leaves button, then button is not true window, and QM will not find it. In future I will work to break this limitation.
I have no ideas about why key T does not work with that window. If you can use Tab manually, then key T also must work.