** Changed in: sikuli
Importance: Wishlist => Medium
** Changed in: sikuli
Status: In Progress => Fix Released
--
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
@skeets
Ok, with version 1.1.1+ I have to leave you with the workaround for now.
Did not find any possibility to change the behavior.
It is on the list for version 2.
--
You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.
@skeets
thanks. fine.
Now I am sure, that I see what you see ;-)
I will keep you informed.
--
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
OK cool glad it's not just me. :P Umm we are using 1.1.1.
Sikuli Version: SikuliX 1.1.1
OS Version: win 6.1
Java Version: 8
Python Version: 2.7.0
--
You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.
@skeets
Some first tests with findAll() tell me:
- exact() does not change the behavior
- a blank image is not found in all possible/expected locations and subsequent
matches overlap
I will have a deeper look into the implementation, but I doubt, that I
can really change something (most of it is
Awesome thanks for the help!
FYI, the workaround is working, a blank child image with some "extra
stuff" is found every time and where we expect it to be within the
parent image using the findall method.
--
You received this bug notification because you are a member of Sikuli
Drivers, which is
@skeets
no problem.
I will try it myself, since I am interested to fully understand the
effect and look, wether it could be corrected somehow.
I will let you know about my results.
--
You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.
Not sure we can use .exact() correct? Based on my info above? We need
to be able to find the blank image at a specific location and if we only
find one image at a location (of possibly many locations) then it may
not be the image at the location we are looking for. Make sense?
--
You received
@skeets
Agreed: an image that has at least some non-blank parts should be found
correctly.
What about .exact()?
--
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
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
@skeets
Yep, that problem is builtin with findAll(): in some margin around a match
another match will not be looked for (speed), which makes sense for non-solid
images. If an image can be found more than once in a region, it is not
predictable (due to the underlying OpenCV feature
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
A clickable grid.
--
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
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
** Changed in: sikuli
Status: New = In Progress
** Changed in: sikuli
Importance: Undecided = Medium
** Changed in: sikuli
Importance: Medium = Wishlist
** Changed in: sikuli
Assignee: (unassigned) = RaiMan (raimund-hocke)
** Changed in: sikuli
Milestone: None = 2.0.0
--
Do you have an example, where findAll() returning 100 matches or even
more might be of value?
--
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
There was a question about this here:
https://answers.launchpad.net/sikuli/+question/172529
Unfortunately the answer given no longer works:
Best Tsung-Hsiang Chang (vgod) said on 2011-09-28: #1
This's not documented yet, but there's a parameter FindAllMaxReturn to
change this.
For
17 matches
Mail list logo
