sikuli-driver team mailing list archive

Thread
Date

[Question #453689]: IDE changes script - similar(1.0) to exact()

To: sikuli-driver@xxxxxxxxxxxxxxxxxxx
From: John Winning <question453689@xxxxxxxxxxxxxxxxxxxxx>
Date: Fri, 10 Feb 2017 19:43:59 -0000
Reply-to: question453689@xxxxxxxxxxxxxxxxxxxxx
Sender: bounces@xxxxxxxxxxxxx

New question #453689 on Sikuli:
https://answers.launchpad.net/sikuli/+question/453689

If I save my script in the IDE (I rarely do this, I use an external editor), I found that the IDE changes similar(1.0) to exact() without saying anything. This caused an incorrect exact match with images of different shades of color - i.e. in shadow. Because the IDE changed my code silently, this was very difficult for me to find. Also, it took me some time to conclude that exact() isn't exact pixel-for-pixel.

I can avoid it by not saving with the IDE. However, I will not be able to use the export packed option. I just discovered this feature, and would like to use it to make sharing easier. I tried to work around the problem by using similar(0.99), but that value still results in an incorrect "exact" match. 

Questions: Is there a way to prevent silent script changes during Save or Exports? What else does the IDE change in scripts? If there is a different approach I should use to find perfect matches, please let me know.

Thanks! 

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