In some applications, the screen may remain unchange while the system is busy and during this point, it may not be possible to interact with the application. Instead of using dummy waits, the ability to wait for the mouse cursor status will help to better manage the RPA design
Hi Eric,
Thanks for getting back. You are right on the usage i had in mind. I am looking at using a wait stage for mouse cursor to be changed back to normal cursor from busy (hourglass).
I am actually using this in Oracle Java application, where the application would still be considered active. However, when certain fields are entered, the mouse cursor becomes hourglass and it will not allow future actions until some background search / processing is completed. As such, i had thought that if we can read the mouse cursor status, that would help in such case. But you are right that developer would have to be mindful that the target application has to remain activated during that wait.
Can you add some additional detail. Are you referring to waiting for the mouse to change from say an hour glass back to standard arrow? Typically, the state of the cursor is dictated by the active application. What happens if your process, in some way, moves the mouse to another application?