sikuli-driver team mailing list archive
-
sikuli-driver team
-
Mailing list archive
-
Message #23488
Re: [Question #242409]: Does sikuli create and use an image cache?
Question #242409 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/242409
Status: Open => Answered
RaiMan proposed the following answer:
No, there is not any magic, that might change a captured image's content automagically.
And currently there is no cache, that might hold images and anyhow not over subsequent script runs or IDE sessions.
So if an image is no longer found though one thinks it should, it always
has something to do with the fact, that the screen content has changed
against the time, the image was captured (though this might not be
obvious to the human looking at the screen).
If for example the background colour changes slightly and the captured
image has much background, then this might lead to a reduced similarity
score, that might lead to FindFailed (score < wanted score or 0.7 in the
standard).
Another reason is rendering: If the rendering scheme changes (might be
e.g. with browsers based on different engines), then the image might
have different pixels usually at the edges of image elements, which in
turn will lead to a reduced similarity.
*** Conclusion:
If an image is no longer found, though it should be found, then you first should check, what has changed in the environment, that is responsible for bringing the grafics on the screen.
You might compare the two images (old and new capture) in an image viewer, that allows to magnify to the pixel level.
--
You received this question notification because you are a member of
Sikuli Drivers, which is an answer contact for Sikuli.