Question #257314 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/257314
RaiMan proposed the following answer: I want to add to Eugenes correct approach: In situations, where after a click action, that should change the screen content, the time to complete this screen change is varying (due to network or other delays), the only way to make such a workflow time efficient AND robust, is to wait for some expected image, that should signal the completion of the screen change after the click or other actions. In some situations the wait for the absence of an image might be used as well (waitVanish()). You might either use Eugene's approach packed in a function or use wait(image, timeout). In both cases the challenge is to decide for a maximum value for the timeout, that is sufficient in most cases. Waiting for an image to appear is much more flexible than time based waits, since no matter, how long you set the timeout, in the moment, the image appears, the script will continue. The maximum delay you have is the time for one search. click(someTarget) wait(someFollowUpImage, maxTimeout) -- You received this question notification because you are a member of Sikuli Drivers, which is an answer contact for Sikuli. _______________________________________________ Mailing list: https://launchpad.net/~sikuli-driver Post to : [email protected] Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
