sikuli-driver team mailing list archive

[RaiMan <rmhdevelop@xxxxxx>]

Thanks. Known problem.

Setting waitScanRate(10) should be sufficient (waits 0 .1 secs), since
faster searches currently are hard to achieve.

The WSR is not added, but is a minimum waitime including the search.

-- 
You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.
https://bugs.launchpad.net/bugs/1162649

Title:
  Region.exists() sleeps even when timeout set to 0

Status in Sikuli:
  Fix Committed

Bug description:
  The Region.exists() function has an unnecessary sleep in it, even when
  the wait time is set to 0 (eg. Region.exists("myimage.png", 0).  The
  shortest possible sleep time is 1/Settings.WaitScanRate, with
  WaitScanRate set to 1000.  Values for WaitScanRate > 1000 are ignored,
  and less than 1000 result in a longer wait time.  I believe that when
  exists() is called with a 0 wait time, then after doing the find it
  should immediately return the result without sleeping for
  1/Settings.WaitScanRate seconds first.

  All that said, as a workaround, the findNow() function can be used for an immediate find instead, as it does not have the extra delay (and is in fact unaffected by the WaitScanRate setting).  So, in code, rather than using:
     Region.exists("image.png", 0)
  instead use:
     (findNow("image.png") != None)

  This was observed in Sikuli X 1.0-rc3 (r905), on a Windows 7 64-bit
  OS.

  Side note:  one might reasonably assume that an extra delay of 1/1000
  of a second might be considered negligible / inconsequential, but I am
  using Sikuli in an application which is being tightly performance
  tuned, and the time to determine whether an image exists in a region
  only takes about 0.2 milliseconds, so the extra 1 millisecond added on
  top really slows things down :-).

To manage notifications about this bug go to:
https://bugs.launchpad.net/sikuli/+bug/1162649/+subscriptions