Sikuli logging into file

If we are talking about writing log messages to a file, then what you want is already possible now:

supposing you have your own global function, that writes your log message to a file, then you can use Debug.setLogfile() to define a file, where the Sikuli log messages are written.
Just using Debug.log() ( [debug] ) will write your own messages into the same file.
Debug.log() can be configured to create message timestamps and there are Debug.action(), Debug.error() and Debug.info() that produce different message headers [log], [error] and [info].

So it is not really clear what you are missing.

What is still missing, but has low priority, is to use a standard logging module. But this would not really change the situation for you, since you would have to use Sikuli features for logging, not vice versa.

An additional option, that might make sense, is to accept a callback function from the user, that is called with the log message from SikuliX, instead of printing it or writing it to a file.
Do you think, this makes sense?

Hi RaiMan,

Thanks for quick answer!
Did you mean that this is available in 1.0.1 or 1.1.0? I am still using 1.0.1 since I wasn't able to install 1.1.0 successfully.
So when I try t set a log file, as you suggested:

Debug.setLogfile("C:\\SikuliX\\Tests\\TRACE.log")

I get the following error:

C:\SikuliX\sikuli-script.jar -r Tests\Test.sikuli
[error] script stopped with error in line 44
[error] AttributeError ( type object 'org.sikuli.basics.Debug' has no attribute
'setLogfile' )

Am I doing something wrong?

And regarding your last question (about accept a callback function from the user), I am not sure what you mean. So if could give a bit more details that will be great!

Thanks again!
Eugene

UPDATE

The command name was wrong and when I changed it to:

Debug.setLogFile(config.traceFile)

that started working fine.

So what I meant, are not just messages that I create, but things like I see on the screen when the script is running. For example:

[log] ( Meta ) TYPE "r"
[log] TYPE "#ENTER"

and the rest of such output (like highlights info as well)

Hope that makes it clear.

Thanks,
Eugene

This is the feature:
After having said:
Debug.setLogFile(config.traceFile)

all messages produced by SikuliX (e.g. highlight) are going to this file.

… but to get your own messages to that file, you have to use
Debug.log()
and the other possible functions.

… so this file cannot be opened/written/closed by yourself additionally.

Ok, now I get it.

So there is absolutely no way to use Debug.log together with my own logging?
I am trying to thing of some workaround to maybe merge these 2 files somehow but it seems like pain to do that. Maybe you have any ideas?

Thanks!

@ comment #6

If you show me your code, how you do your logging (might send it to me privately), then I am sure I can tell you what to do.

Thanks for your answer RaiMan!
I was not familiar with that term (callback function).

I will play with that idea and see how I can implement it.

Thanks RaiMan, that solved my question.