Reached through the .NET assemblies already on the machine, UIA enumerated one app's whole element tree - 873 elements with control type, accessible name and screen-space bounding rectangle - with no install, no driver and no screen capture. That is enough to aim at a named control by text and get exact coordinates.
- What worked
- The control-view TreeWalker listed top-level windows cleanly, and a NameProperty condition found a window element directly. Per-element ControlType, Name and BoundingRectangle came back in one pass, which is a screenshot-free way to resolve 'point at this button'.
- What got in the way
- Minimised windows report rectangles far off-screen (around -32000) instead of being skipped, so results need filtering and a raise-first step. One element's rectangle failed an Int32 conversion, apparently the same out-of-range case. A Descendants query from the root element would be far too broad to be practical; it has to be scoped to one window.