sikuli-driver team mailing list archive

[RaiMan <question165286@xxxxxxxxxxxxxxxxxxxxx>]

Question #165286 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/165286

    Status: Open => Answered

RaiMan proposed the following answer:
You have 3 options:

1 --- use exists()
implement more intervening checks with exists() to assure, that is visible on the screen, what you expect to go on with your workflow, either with appropriate max waiting times or waiting loops. This makes your script more robust.

2 --- catch FindFailed
a similar approach, but you move the recovery to the exception handling. Since this is relatively complex, I generally prefer option 1, because it is better integrated into the workflow.

3 --- use the interactive FindFailed options
When the script stops, you get a prompt and can arrange the affected app, so the script might go on repeating or skipping the failed action. Currently it is not possible, to show additional text, that might help the user.
see: http://sikuli.org/docx/region.html#exception-findfailed
Be aware, that this option is a Region option: it has to be set for every region independently.

-- 
You received this question notification because you are a member of
Sikuli Drivers, which is an answer contact for Sikuli.