Hi Ben,
First, lemme say that your advice is good. I agree that Search Padding is a good technique to use in many situations, but typically I don't suggest it when someone first starts using Surface Automation since it's only necessary in niche situations where, for example, two buttons look exactly the same. I want to ask about something you brought up in case I've missed something.
What makes you say that using Anywhere isn't performant? I understand that the BP docs indicate that is the case, but I assume that was more of a theoretical concept because in practical use, it is pretty fast. In fact, Surface Automation using the Anywhere is faster than AA, UIA, and Browser mode most of the time. The only exception is potentially using Win32 or Browser mode with CSS Selectors, XPath Expressions, or Absolute XPath which would likely be a similar speed. For example, I made an automation that uses almost entirely Surface Automation, and all of the elements (at least all of the anchor elements) are set to Anywhere. Granted, specific elements that need to be clicked were often using relative, but their anchor elements were using Anywhere. It automates an RDP window that remotes into a server where Blue Prism cannot be installed. So, it is searching using Anywhere across a 1920x1080 surface area with tons of elements on the screen.
If you have a suggestion for how I can reproduce Surface Automation (in v6) being slow using Anywhere, I'd absolutely like to try it because I'm always looking to know ahead of time what limitations I may run into.
Thanks!
------------------------------
Dave Morris
Cano Ai
Atlanta, GA
------------------------------
Dave Morris, 3Ci at Southern Company