sikuli-driver team mailing list archive

[Donald Hines <question199027@xxxxxxxxxxxxxxxxxxxxx>]

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

Donald Hines posted a new comment:
Well, I'm going to have to give up on this.

I can handle the flaky ocr.  It's usually possible to find strings that
the ocr can identify fairly reliably.  But the bizarre inconsistency of
the text search is just too difficult to work around.   It seems to work
differently from day to day, and code that I had working yesterday will
suddenly decide on the next day that it will NOT find strings that
region.text() shows the ocr has correctly translated.  The same strings
that it WOULD find yesterday.

I was able to get around the bugs in the wait("text") function by simply
writing my own.  But for wait I only needed to identify that a string
EXISTS in region.text().  For finding places to click, I MUST be able to
figure out where those strings are on the screen.  I could write a
function to break the screen up into smaller and smaller regions and
locate the text that way, but it would be TERRIBLY slow.

I think the way we will have to deal with this is to use graphic
searches and either insist that anyone using the tool have the same
theme and screen resolution, OR we might run the code in a Virtual
Machine.

Sikuli is an AWESOME tool, we just happen to need functionality that
isn't fully functional yet.

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