Microsoft Windows Automation API 3.0

[skyline-gleb]

Research #47 showed:

• UISpy used UIAutomation* references from .NET Framework (Cruciatus too)
• VisualUIAVerify used UiaComWrapper (with Interop.UIAutomationClient) spreaded with Windows Kits or VisualStudio

Advantages of using UiaComWrapper:

• Cruciatus sees the needed elements from ToolStripButton placed after ToolStripComboBox not found in WinForms app #47

Disadvantages of using UiaComWrapper:

• Control tree changed for some elements, for example, ComboBox in windows save as dialog
• Many elements stopped to implement some automation patterns
• Not included in .NET Framework (but may be project can help)

Needed changes for using UiaComWrapper in baddc0a commit. Or see draft/use-uiacomwrapper-lib branch.

[skyline-gleb]

Inspect uses the LegacyIAccessible notion, and we may be can to use both libraries

[skyline-gleb]

With API 3.0 we can support windows 8.1 desktop apps.. (test on win8.1 calculator)

[testcbackup]

How to find elements if UISpy and inspect tool does not display value for it

[repon06]

how to get the item LegacyIAccessible.Value?