sikuli-driver team mailing list archive

[skeets <skeets.malloy@xxxxxxxxx>]

OK thanks for the info and suggestion!!  Makes more sense now.

For us, we need to be able to find the expected (child) image at the
expected coordinates within the parent image for our test to pass.
Those expected coordinates may not always be at 0,0 within the parent
image.  So in order to find the child image (the blank image in
question), we thought we needed to use the findall method since in this
case the child image can be found in many places within our parent
image.  So we loop through all of the findall matches testing the match
coordinates against our expected coordinates.  So it doesn't seem to me
that we could use your suggestion if I understand correctly?
Unfortunately we can't scale down our parent image any further or else
it will not be unique enough on our screen.  BUT we can update our
"blank" image to not be blank anymore.  We are testing a field to see if
it has an icon or not and that field has a neighbor field that is never
blank so think we can also get around this issue with a bigger child
image that includes part of the neighbor field.

-- 
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