sikuli-driver team mailing list archive

[RaiMan <question184410@xxxxxxxxxxxxxxxxxxxxx>]

Question #184410 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/184410

RaiMan posted a new comment:
more aspects:

-- challenge: performance:
Even taking into account, that the subsequent searches in a group can be done in restricted regions, the total time will add up to some seconds. This might not be acceptable in many situations.

-- challenge: how to restrict the search area
example: If you are searching something right of a given match/region, the search area extends to the screen border and has the height of the given match. If the searched image does not fit into the region, it will not be found. So this is a challenge for the capture process. Or you have to add some extra margins to the search areas, to be "capture fault tolerant".

-- challenge: get the correct next match
If there is more than one match in the restricted area for the next element: which one to take? To have a chance to make a decision (e.g. the nearest one), you have to use findAll() (which extends the search time further). A simple find does not guarantee to return the expected match.

-- challenge: speed things up
The only approach to speed things up beyond restricting the search areas is to search the pattern elements in parallel. But then you have to search all elements on the whole screen or add some additional hints, to restrict the search areas, since you do not have any match information yet. 

I will now make some tests in these challenge areas.

You received this question notification because you are a member of
Sikuli Drivers, which is an answer contact for Sikuli.