You can bump that timeout as high as you need to. It's a timeout so if the object returns before the time is up, it will stop waiting.
Thanks for the response. Please mark a reply on this thread as a solution if we were able to help you.
Hi egiacomi,
What exact object recognition issues did you face? I will appreciate if you post here the screenshots illustrating the issue.
Hi TanyaYatskovska ,
I solve partially the issue, the vm has an hardware less powerful in front a physical pc, after some tests i try to increment the delay between events to 3000 ms and this change solves more or less 80% of errors .
For the other errors at the moment I haven't a solution , an example is this :
P.S.
the VM has 4 CPU and 8 GB of ram .
Thanks for the support
Emanuele
That would do it. So, the object recognition errors are due to timing, where the application isn't displaying the forms as rapidly as you expect it to.
Couple of things you can do to correct... you found one. The Auto-Wait timeout in Tools | Options will help with that.
You can also write into your code judicious places where you use a WaitChild or WaitAliasChild call to wait for an object to show before proceeding.
But I think, generally, you're on the right track here.
I have already implemented in my project WaitChild call .
I set auto-wait timeout to 10000 ms .
At the moment i haven't other ideas to the last errors but I'll continue to do other tests hoping to find the solution .
Emanuele
You can bump that timeout as high as you need to. It's a timeout so if the object returns before the time is up, it will stop waiting.
Thanks for the response. Please mark a reply on this thread as a solution if we were able to help you.
