Question #270582 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/270582
Status: Open => Answered
RaiMan proposed the following answer:
-- yes, the problem is fixed in 1.1.0
-- (r.exists(p/similar(.9f), 0)
will return after the time needed to find p in r, which depends on the sizes of
r and p
using a waittime of 0, lets the search always return after one try. So
in this case WaitScanRate is not relevant.
WaitScanRate defines how often the search is repeated during the
waittime, if waittime > 0
Settings.WaitScanRate = 100;
would only make sense, if the search time in the average is less than 10
millisecs (which only is the case with very small regions).
the standard WaitScanRate is 3. Higher values usually only lead to constant
search, since the average search time is greater than the scan interval of some
10 millisecs.
Constant search is very greedy, since it is plain number crunching.
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 : sikuli-driver@lists.launchpad.net
Unsubscribe : https://launchpad.net/~sikuli-driver
More help : https://help.launchpad.net/ListHelp
