Recording Window names instead of mouse coordinates?

[MC256]

Thank you for the information. I can see that these single-step recorders (Window, Control, Accessible Object, HTML Element, Image, etc...) can be very useful, each in their own right. It would perhaps be too complicated to use all these information sources in the general purpose recorder. But still... it is something to think about for the future. An "accessibility" mode of the recorder which tries its best to track interactions by window/control/class/role/accessibility attributes and not by coordinates. Okay, enough about that.

I like how QM helps you build the calls to the various functions and parameters necessary to automate, given the challenges of the particular app: Win32 HWND/Accessible/IHTMLElement COM, Image recognition, etc. I think I am sold.

Now for a big question: When is MSUIA support coming?