Question #262951 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/262951
Status: Open => Answered
RaiMan proposed the following answer:
-- setFindFailedResponse(SKIP)
This suppresses any FindFailedd reporting.
So how do you realise "image matching will time out mostly"?
-- The wheel() function and the if() function aren't called within the for
loop, so the slowdown is caused by those.
what do you mean by that?
They are indeed inside the loop.
-- so what do you mean by slowdown?
... that the cursor does not move anymore?
if yes, then together with the switching-findfailed-off and using the
getLastMatch() feature the cursor will not move in case of find failed (which
is skipped), since there is no new last match.
So to get nearer to the problem, you should eliminate the
setFindFailedResponse(SKIP) and replace the wait(image) with exist(image)
(which suppresses a FindFailed exception and hence can be used with if).
In the places, where having a new match is vital, you should then either use
wait(image) or if not exist(image): and do something that makes sense.
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
