sikuli-driver team mailing list archive
-
sikuli-driver team
-
Mailing list archive
-
Message #09811
Re: [Question #193287]: Problems when running javaw.exe or java.exe with hidden console
Question #193287 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/193287
RaiMan posted a new comment:
--- I do have some more questions
Some of the topics you mentioned are touched upon in one or more faq's.
https://answers.launchpad.net/sikuli/+faqs
--- javaw and logging
since stdout is written to null, you have to use some logging feature that writes to a file.
e.g. faq 1778
--- observe vs waits, etc
it is more:
(observe() vs. wait()/exists()) vs observe(,background = True)
In general observe uses handlers (like with the hotkeys), so code gets a little bit harder to read.
With wait()/exists() you can "read" the workflow when looking through a script.
Usually observe is more economic, when you have to wait for more than 2 or 3 events in parallel.
The situation with observe in background is totally different, since your script continues, while the observations are spawned. The challenge here is the communication between the handlers and the main workflow.
--- Anyway, thanks for taking the time
Thanks for the feedback in detail. Might help others to think about using AutoIt ;-) in combination with Sikuli (like AppleScript on Macs), to solve some things missing in Sikuli.
... and in many cases, talking in detail about a problem helps a lot to
solve it ;-)
Always welcome with additional questions.
--
You received this question notification because you are a member of
Sikuli Drivers, which is an answer contact for Sikuli.