sikuli-driver team mailing list archive

Thread
Date

[Question #253839]: Sikuli console debugging logging show unreadable characters when logging key strokes

To: sikuli-driver@xxxxxxxxxxxxxxxxxxx
From: TheHappyRock <question253839@xxxxxxxxxxxxxxxxxxxxx>
Date: Sat, 30 Aug 2014 19:32:50 -0000
Reply-to: question253839@xxxxxxxxxxxxxxxxxxxxx
Sender: bounces@xxxxxxxxxxxxx

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

Example output:

"Executing open_session with the following parameters: {'session': 'Session'}

[log] CLICK on (67,101)
[log] CLICK on (169,133)
[log] TYPE "î€ˆ"
[log] TYPE "î€‚"
[log] Shift+TYPE "î€"
[log] TYPE "î€’"
[log] Ctrl+TYPE "c"
[log] TYPE ""
[log] TYPE "î€‚"
[log] Shift+TYPE "î€"
[log] TYPE "î€’"
[log] Ctrl+TYPE "c"
[log] TYPE ""
[log] CLICK on (12,178)
[log] TYPE ""

This output is captured by redirecting stdout/err to file when running command line using the sikuli scripts which turn utf logging on and debugging.

Those odd characters are often things like Arrow keys and such. Is there anyway to get readable output without having to pull up tests to see what it is trying to do when there is an error?

Thanks for the help!

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