Thanks for the answer, Angelo.
If the Wait for Window to Appear command waits for the elements on the window, this is probably what is going on.
Also, I did notice that the execution without Debug Mode is faster in detecting the window. It takes around 15s instead of the 1 minute.
Looking at the documentation I did not understand exactly what the "Safe Search" parameter does. It says "When enabled, a higher performance window search algorithm is executed". The higher performance is related to how faster it executes or to how well the detection occurs (probably looking "deeper" and being slower)?
Regards
------------------------------
Vinicius Marques
------------------------------
Original Message:
Sent: Wed May 12, 2021 10:00 AM
From: Angelo Alves
Subject: Wait Window taking too long
Hi,
It is difficult to speak without doing some tests. The time of the command takes into account some factors, including the number of elements on the screen and if after it opens (10sec) the system is loading information in the background because the command is waiting to map all the elements in the cache.
What you can test is:
- Enable "Safe Search"
- Remove the "Class name" using only the "Process Name" and Regular Expression
Regards
------------------------------
Angelo Alves
Original Message:
Sent: Fri May 07, 2021 04:07 PM
From: Vinicius Marques
Subject: Wait Window taking too long
Hi,
I would like to understand better how the Wait Window command works. I have one window that is taking 1 minute to find and I can see the window on the screen and interact with it is less than 10 seconds. Anyone ventures to say what could be happening or, better yet, how to fix it?
Command:
waitWindow --useregex --regexPattern "Transações de imposto .*" --regexOptions "Compiled" --classname AxTopLevelFrame --processname Ax32 windowImposto=value
------------------------------
Vinicius Marques
------------------------------