sikuli-driver team mailing list archive

[f <question293475@xxxxxxxxxxxxxxxxxxxxx>]

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

f posted a new comment:
Thanks to both of you for the answers
I will then have 2 questions.

First yes, lowering the similarity is not an option. I'm pretty high (95
for clicking, 99 for searching), but even by lowering a lot, it either
still doesn't find, or generate false positives.

I already implemented some utilitary functions, and I have something kind of convenient to have sikuli screenshots and names when necessary. I'll give 1.1.1 a try though.
First question: when is v2 planned to be released?

Anyway, ok, I will see if the project is still viable with a set of image for each os...
And so am trying to reduce the number of images.

So for clicking, I will use your solution of defining the location of
the clicking zone per coordinate, it works well

But for searching if a UI element looks like it should be, I naturally cannot use coordinates, I need a screenshot. 
The problem now is that there is a lof of UI elements which can be slightly changed. So if I change all elements and check that the whole interface is as it should be, it doesn't work: because if one element is slightly different, I still have a general match of 99.
To make it work, I need to compare each small zone separately with how they should be, then I have a negative match when I should have.
So my idea was to have only one image of the ui fully modified, and then defining a zone in the image, and searching this zone on screen. But I don't find how to do it. Any clues?
(Is it clear? I mean having a screenshot of the ui totally modified, but searching on the screen only a part of this image)
Or any other alternative maybe?

Thanks again

-- 
You received this question notification because your team Sikuli Drivers
is an answer contact for Sikuli.