Sikuli console debugging logging shows unreadable characters when logging key strokes

Asked by TheHappyRock

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. Platform is linux using a Konsole or Jenkins.

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!

Question information

Language:
English Edit question
Status:
Answered
For:
SikuliX Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
RaiMan (raimund-hocke) said :
#1

You seem to use 1.0RC3.
Nothing to do there, to correct this.
You have to "learn" the meaning.

With version 1.0.1+, the log output for function keys is readable (e.g. Key.DOWN is logged as #DOWN.)

Can you help with this problem?

Provide an answer of your own, or ask TheHappyRock for more information if necessary.

To post a message you must log in.