Question #242870 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/242870
Status: Needs information => Answered
RaiMan proposed the following answer:
This seems to be caused by the fact, that you use ----sikuli-
api-1.0.2-standalone.jar together with SikuliX version 1.0.1 stuff.
This is not tested and might lead to problems.
So just start with a clean SikuliX test usage in D:\SOFT\sikuli\:
- delete everything exept sikuli-setup.jar
- run setup and select option 4 (option 1 might be selected too, to have the
SikuliX IDE available for image management)
- this should succeed and give you sikuli-java.jar (and optionally
sikuli-ide.jar)
Now take care, that in your projects class path you only have a reference to
sikuli-java.jar (do not move it!) for any Sikuli stuff.
In your test app before touching any SikuliX features (like e.g. Screen s = new
Screen();) add this:
java.lang.System.setProperty("sikuli.Debug", "3")
this will produce some more debug output on command line, that helps to
understand, what's going on.
If you want to use sikuli-api-1.0.2 in parallel in the same project just
put it in a separate folder than D:\SOFT\sikuli\, add a reference to
your projects class path, add an import and test this.
BTW: I guess you know that already: sikuli-api-1.0.2 is in no way API
compatible to SikuliX, it is only the basic features they have in
common.
--
You received this question notification because you are a member of
Sikuli Drivers, which is an answer contact for Sikuli.
_______________________________________________
Mailing list: https://launchpad.net/~sikuli-driver
Post to : [email protected]
Unsubscribe : https://launchpad.net/~sikuli-driver
More help : https://help.launchpad.net/ListHelp
