in reply to Re^2: Assist human unobtrusively in a 3rd party Windows GUI
in thread Assist human unobtrusively in a 3rd party Windows GUI

My advice is to not send mouse clicks but to use keyboard navigation/hotkeys or to send window messages with the ID of the target control to activate it.

I am not sure what you mean by this? We (my fellow users who are affected by this) have not been able to find any kind of keyboard sequence that would have the effect of clicking upon this button. If we had found such a thing, then I could push a keyboard button to send a keyboard macro. Pushing a single keyboard button would be less terrible than it is now (move hand to mouse, move cursor to "reset", click it, move cursor back to original window, click, put hand back on keyboard). I suspect that you are telling me something about the GUI_Test UI that I don't understand. send window messages with the ID of the target control to activate it sounds like what I need to do.

  • Comment on Re^3: Assist human unobtrusively in a 3rd party Windows GUI

Replies are listed 'Best First'.
Re^4: Assist human unobtrusively in a 3rd party Windows GUI
by Corion (Patriarch) on Dec 16, 2020 at 07:09 UTC

    Ooof - if the application is not accessible in the sense of being navigable by keyboard alone, then yes, you will need to send mouse clicks (or window messages of the type WM_CLICK).

    If you can find the control ID of the button (using the spy.pl program), you can make your click-sender somewhat more resilient by sending the window message to that control, otherwise you need to send it using x/y coordinates and need to hope that nothing changes the layout of the window (font choice, font size, zoom/scaling settings, ...)

Re^4: Assist human unobtrusively in a 3rd party Windows GUI
by Anonymous Monk on Dec 16, 2020 at 13:23 UTC