sikuli-driver team mailing list archive

[RaiMan <rmhdevelop@xxxxxx>]

a grid is a grid, because it has some regular row/column structure.
If you act on a grid with Sikuli, you somehow have to evaluate this structure, if it is not known anyway or might vary.

the row and column structure can be evaluated best with some find/findAll in horizontal/vertical direction in limited space (left column/ top row).
If the grid has even elements, this is sufficient. If it does not have even elements, findAll would not help anyway.

Since in a grid you usually want to access a cell, this is best represented by a pair of row and column number like
click(myGrid(row, column))

... and I think, the evaluation to be done in the function myGrid is
much more complicated with the results of a findAll than with the above
approach.

BTW: version 1.1.0 has a feature to define a grid on a region and then
access rows, columns and cells as subregions.

... and there are many people out there, that invest in complicated
scripting in clicking around in Excel sheets, because they do not know,
that there are powerful libraries to access the sheet content directly
(like xlrd for Python/Jython)

conclusion: I do not agree, that a grid is a suitable example for the
need of a findAll returning hundreds of matches.

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