sikuli-driver team mailing list archive

Thread
Date

[Question #273267]: Can we add a parameter to find or watch to return the final images

To: sikuli-driver@xxxxxxxxxxxxxxxxxxx
From: Tak Eda <question273267@xxxxxxxxxxxxxxxxxxxxx>
Date: Tue, 27 Oct 2015 23:13:09 -0000
Reply-to: question273267@xxxxxxxxxxxxxxxxxxxxx
Sender: bounces@xxxxxxxxxxxxx

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

I see that Sikuli downsamples the candidate and expected images (unless we use exact()) before sending them to the matching engine

Can we add a parameter to find or watch to return/request the final processed images being sent by Sikuli to the matching engine (the candidate and expected images)?

My issue is that I have some images with heavy background color and the Sikuli script has a lot of trouble locating the expected image. I would like to see what the actual data being sent to the matching engine is like.

Would adding such a parameter be too much work? Perhaps we can just get two bytearrays that we can write out or something similar to capture()?


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