sikuli-driver team mailing list archive
-
sikuli-driver team
-
Mailing list archive
-
Message #34256
Re: [Question #270538]: Is there a way to remove the sikuli import feature in the nightly build?
Question #270538 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/270538
Status: Answered => Open
Ryan is still having a problem:
Thanks!!
We are using the single .sikuli folder only as the entry point. It is called via 'java -jar sikuli-script.jar -r c:\path\to\executor.sikuli --args [arguments]'. It seemed like the easiest hands-off way to do it. There are several projects running with shared packages and test tools, so the executor.sikuli path is programatically changed based on what project is being run. In some projects there are images with this file and in some there are not but since it is being called from the command line we wanted to make sure it wasn't included in the project package (or even on jythonpath since it should never be called by another Jython script).
Are you saying I could simply begin a Jython session and call the .py
instead of going through the sikuli jar file?
The import is working now, but when I attempt to find the image via
absolute path it is returning
FindFailed: null
Line 2520, in file Region.java
I tried making it a pattern as well. When printing the variable I do see
the path to the proper image, however.
--
You received this question notification because you are a member of
Sikuli Drivers, which is an answer contact for Sikuli.