Question #664713 on Sikuli changed:

RaiMan proposed the following answer:
ok, made some tests.

It principally works, but there is indeed a problem, which is
implemented ;-)

Especially with web-content some image might already be visible on the screen, 
but is not yet in its final place.
Same goes for the other situation, where something should change, but is still 
visible in that moment.

Since the frame buffer is constantly working in the background refreshing the 
content from remote and the taking of screenshots is not synchronized with a 
somehow "stable" frame buffer, these effects might happen.
Only inserted wait()'s can help, to give some time for getting stable/changed. 

so in your case:
wait(1) # adjust the waitime as needed - shorter or longer

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

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to