sikuli-driver team mailing list archive

[skeets <skeets.malloy@xxxxxxxxx>]

This also affects me too in a similar fashion.

I have an image of a certain size and it is a blank image (16x25, RGB is
0, 0, 0).  I find a larger (parent) image using Region exists method
(244x25).  Then from that parent image, I do a sub-verify using the
findAll method to find the smaller blank image. My blank image can be
found in many places within the parent image.  The location within the
parent image that it should find it at is 0,0 but it never finds it at
that location.  The closest it seems to find it is at 2, 0 (which is
also a valid location to find the blank 16x25 image).   I had a larger
parent image that I scaled down because I too thought that the number of
finds is limited to some number.  The scaled down version STILL does not
find the child image within the parent image at 0,0... it only finds it
at other locations...  which is now limited to maybe 35 places...  If I
change up my images and use any child image other than a blank image it
seems to find the image at the location I expect.

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

Title:
  findAll limited to 100 matches

Status in Sikuli:
  In Progress

Bug description:
  Calls to findAll seem to report at most 100 matches., silently
  discarding any further matches.  Suggest findAll be configurable to
  specify the maximum number of matches, even if the default is 100, in
  the same way that similarity defaults to 0.7 but can be configured.
  Also suggest that if the max is exceeded, an exception is thrown so
  that missing matches can be spotted easily

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