sikuli-driver team mailing list archive

[Daniel Ford <question220729@xxxxxxxxxxxxxxxxxxxxx>]

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

A year or two back I managed to create a Sikuli 0.10.2 script that clicked some buttons in Surcode to start an encode session and later close Surcode when encoding finished.  After a number of major PC crashes and reinstallations of Windows 2000 Pro SP4, I tried to run that script again recently and found that it only half worked (it started the encoding but didn't recognise when it finished).

So I downloaded and installed Sikuli X (after uninstalling 0.10.2) and started trying to 'fix' my script.  I got the script to the point that, when run from within the IDE it ran perfectly with no reported errors.  But when I run the 'executable' version from my batch file (the Surcode session is just one part of a long multi-program process!), after  starting the encode process (clicking the <Encode> button) I get a screen full of error messages(?).  Neither a standard Windows error pane nor a DOS box, but a full-screen light-grey background with many lines of text.  The worst part is there are obviously lines of text 'above' and 'below' the top and bottom of the screen, but I cannot scroll the screen with either mouse or keyboard.  <Esc> closes it and returns to my batch file.

I wanted to post a screen-dump of these errors here, but don't see a button for attachments, like most good forums have!  Likewise I can't post my code here (including image patterns).  But I'll include the text from DTSreenc.py here, in case it's useful:
-----
Region(274,509,100,36).inside().click("1359700184703.png")
wait(1)
Region(279,510,89,34).inside().wait(Pattern("1359700210343.png").similar(0.91), 180)
Region(726,181,47,38).inside().click("L1.png")
exit()
-----
The first two images are identical, and are the <Encode> button (which 'greys-out' while encoding, and returns to normal when finished).  The third image is the <X> to close the Surcode program.  [The first two regions could/should be identical, but since the (undocumented!!) Sikuli IDE only creates them by dragging, it's not easy to make them identical.]

So how does one debug a script under these circumstances?  The error messages I *can* see mean nothing to me, and the possibly more important first and last messages (that I might be able to decipher) are off screen and inaccessible!

Any suggestions will be appreciated.

Rgds, Daniel

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