Order of matches / image scan

Hello,

It's probably because there is no need to slow down the function for something, we can perfectly do our-self.

Try this :
for item in sorted(findAll("img.png"), key=lambda m:m.y):
    print item

You will find every information here :
http://doc.sikuli.org/region.html#finding-inside-a-region-and-waiting-for-a-visual-event

Regards.

Hi obiwan,

Thanks for the response. My question was indeed to know if always starting from (0,0) was considered sub-optimal - was there an optimization like "most probably the next click/find will be for an item below the current one, so lets start the search from here...".. Again, asking purely from an interest to know the internals..

every new find (or the implicit find in a new click) will always search in the given region (might be the screen).
So you most probably get the same matches again.

If you want a different behavior, you have to define a restricting region, based on the last match, that you want to exclude from further finds.

But sounds like an interesting idea: it should be checked (I will do that), wether we can define regions to be searched, that contain "no-go-areas", which would allow to repeat the same find on the same region, after having "subtracted" the area containing the last match.
Which corresponds with another request, that wants to find with an image, where parts are excluded from the image (e.g. some inner part containing text, that might change (localized buttons)).