Re: [Sikuli-driver] [Question #248604]: Sikuli logging into file

2014-05-13 Thread RaiMan
Question #248604 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/248604 Status: Open = Answered RaiMan proposed the following answer: 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

Re: [Sikuli-driver] [Question #248604]: Sikuli logging into file

2014-05-13 Thread Eugene S
Question #248604 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/248604 Status: Answered = Open Eugene S is still having a problem: 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

Re: [Sikuli-driver] [Question #248604]: Sikuli logging into file

2014-05-13 Thread Eugene S
Question #248604 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/248604 Eugene S gave more information on the question: 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

Re: [Sikuli-driver] [Question #248604]: Sikuli logging into file

2014-05-13 Thread RaiMan
Question #248604 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/248604 Status: Open = Answered RaiMan proposed the following answer: This is the feature: After having said: Debug.setLogFile(config.traceFile) all messages produced by SikuliX (e.g. highlight) are going to

Re: [Sikuli-driver] [Question #248604]: Sikuli logging into file

2014-05-13 Thread RaiMan
Question #248604 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/248604 RaiMan posted a new comment: … so this file cannot be opened/written/closed by yourself additionally. -- You received this question notification because you are a member of Sikuli Drivers, which is an

Re: [Sikuli-driver] [Question #248604]: Sikuli logging into file

2014-05-13 Thread Eugene S
Question #248604 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/248604 Status: Answered = Open Eugene S is still having a problem: 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

Re: [Sikuli-driver] [Question #248604]: Sikuli logging into file

2014-05-13 Thread RaiMan
Question #248604 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/248604 Status: Open = Answered RaiMan proposed the following answer: @ comment #2 -- callback option something like this: # your log function def log(msg): global logfile try: logfile

Re: [Sikuli-driver] [Question #248604]: Sikuli logging into file

2014-05-13 Thread Eugene S
Question #248604 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/248604 Status: Answered = Solved Eugene S confirmed that the question is solved: Thanks RaiMan, that solved my question. -- You received this question notification because you are a member of Sikuli Drivers,

Re: [Sikuli-driver] [Question #248604]: Sikuli logging into file

2014-05-13 Thread Eugene S
Question #248604 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/248604 Eugene S posted a new comment: 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. -- You received this

[Sikuli-driver] [Question #248604]: Sikuli logging into file

2014-05-12 Thread Eugene S
New question #248604 on Sikuli: https://answers.launchpad.net/sikuli/+question/248604 Hi RaiMan, This is the third time I am asking the same question. Sorry for that :) Here is the link to the last time I asked it: https://answers.launchpad.net/sikuli/+question/234625 So what I am interested