sikuli-driver team mailing list archive

[RaiMan <question664302@xxxxxxxxxxxxxxxxxxxxx>]

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

    Status: Open => Answered

RaiMan proposed the following answer:
--- seems it matches the target against the same screenshot 
NO - it does not!
When using a search, that waits for an image (like with click(image) or wait(image)), during the given duration (standard 3 seconds) every new trial is started with a new screenshot (waiting would not make sense otherwise ;-)
How often the search during the waiting time should take place is controlled by the scanrate (standard 3 meaning 3 times per second). If a capture/search takes longer than 333 msecs (searching on whole, large screen), it may slow down to 1 - 2 trials per second.

So if your close button is visible on the screen during the search
trials, the search region fits and the captured image is ok, then it
should be found.

If not, then usually the image is bad or the waittime too short.

--- Is there anyway to keep screenshots Sikuli take during running?
Not a feature in your sense (to control the internal image search)

But to solve your problem, have a look here:
http://sikulix-2014.readthedocs.io/en/latest/region.html#exception-findfailed

e.g. using the prompt feature during development of a new script or for
debugging.

Switching on debugging in a script using
Debug.on(3)

might give you also more information about what SikuliX is doing
internally

-- 
You received this question notification because your team Sikuli Drivers
is an answer contact for Sikuli.