Forum Discussion
While the image comparison obviously works for detecting if something shows up... that's not exactly the way I'd go about doing it. However, I'm assuming you have a reason for using a Regions.Find to find a button rather than checking for the existance of the object in your application using something like WaitChild or WaitAliasChild or FindChild or something.
Is there a reason why you aren't using those methods? Basically, FindRegion simply returns another image so you're not actually finding the button, you're just searching one picture for another picture. In order to actually interact with the button, I'd suggest using FindChild. What you could do, then, is use FindChild to search for the object and then, if it's find, click on it and if it's not found, log the error.
Related Content
- 6 months agomengbinhao
- 12 months agoMW_Didata
- 2 years agorkadali
Recent Discussions
- 2 days agoGane195