Re: [Sikuli-driver] [Question #698112]: Windows 10: imports no longer working after moving to newest version (run from comand line, sys.path not containing location of common modules)

Question #698112 on SikuliX changed: https://answers.launchpad.net/sikuli/+question/698112 RaiMan proposed the following answer: --- sites.txt I admit, that the current implementation is a bit complicated. - start the IDE - File Menu -> Open Special files - 3 - the sites.txt file is opened for

Re: [Sikuli-driver] [Question #698112]: Windows 10: imports no longer working after moving to newest version (run from comand line, sys.path not containing location of common modules)

Question #698112 on SikuliX changed: https://answers.launchpad.net/sikuli/+question/698112 Richard Chubb posted a new comment: --- my repacked SikuliX IDE jar for the sites.txt solution, there is no need to pack anything into the SikuliX IDE jar. A path given in sites.txt is simply added to

Re: [Sikuli-driver] [Question #698112]: Windows 10: imports no longer working after moving to newest version (run from comand line, sys.path not containing location of common modules)

Question #698112 on SikuliX changed: https://answers.launchpad.net/sikuli/+question/698112 RaiMan proposed the following answer: got it :-) -- You received this question notification because your team Sikuli Drivers is an answer contact for SikuliX.

Re: [Sikuli-driver] [Question #698112]: Windows 10: imports no longer working after moving to newest version (run from comand line, sys.path not containing location of common modules)

Question #698112 on SikuliX changed: https://answers.launchpad.net/sikuli/+question/698112 Richard Chubb posted a new comment: just sent you an email -- You received this question notification because your team Sikuli Drivers is an answer contact for SikuliX.

Re: [Sikuli-driver] [Question #698112]: Windows 10: imports no longer working after moving to newest version (run from comand line, sys.path not containing location of common modules)

Question #698112 on SikuliX changed: https://answers.launchpad.net/sikuli/+question/698112 RaiMan proposed the following answer: --- my repacked SikuliX IDE jar for the sites.txt solution, there is no need to pack anything into the SikuliX IDE jar. A path given in sites.txt is simply added to

Re: [Sikuli-driver] [Question #247134]: "from org.sikuli.script.natives import Vision" statement not working

Question #247134 on SikuliX changed: https://answers.launchpad.net/sikuli/+question/247134 RaiMan posted a new comment: --- 2.0.5 vision is no longer supported since many versions (not sure since when). It was no longer relevant with the new implementation of OpenCV at the Java level. Just

Re: [Sikuli-driver] [Question #247134]: "from org.sikuli.script.natives import Vision" statement not working

Question #247134 on SikuliX changed: https://answers.launchpad.net/sikuli/+question/247134 Richard Chubb posted a new comment: also does not work for 2.0.5. Where is vision now located? -- You received this question notification because your team Sikuli Drivers is an answer contact for

Re: [Sikuli-driver] [Question #698112]: Windows 10: imports no longer working after moving to newest version (run from comand line, sys.path not containing location of common modules)

Question #698112 on SikuliX changed: https://answers.launchpad.net/sikuli/+question/698112 Richard Chubb posted a new comment: Hi, thanks for that RaiMan. With the hardcoded path in sites.txt, in my repacked SikuliX IDe jar, the common modules were imported. although now I have a new different

Re: [Sikuli-driver] [Question #698112]: Windows 10: imports no longer working after moving to newest version (run from comand line, sys.path not containing location of common modules)

Question #698112 on SikuliX changed: https://answers.launchpad.net/sikuli/+question/698112 RaiMan proposed the following answer: ok, completely understood. Supposing you are using the SikuliX IDE jar, I will create a modified 2.0.5 version until monday for you, that accepts

Re: [Sikuli-driver] [Question #698112]: Windows 10: imports no longer working after moving to newest version (run from comand line, sys.path not containing location of common modules)

Question #698112 on SikuliX changed: https://answers.launchpad.net/sikuli/+question/698112 Description changed to: I am having the same issue as in https://answers.launchpad.net/sikuli/+question/265660 I have followed the suggestions in that question but it has not resolved my issue. I get the

Re: [Sikuli-driver] [Question #698112]: Windows 10: imports no longer working after moving to newest version (run from comand line, sys.path not containing location of common modules)

Question #698112 on SikuliX changed: https://answers.launchpad.net/sikuli/+question/698112 Richard Chubb posted a new comment: The sites_examples.txt states # rename/copy this file as sites.txt and it will be seen by SikuliX # # add absolute paths one per line, that point to other

Re: [Sikuli-driver] [Question #698112]: Windows 10: imports no longer working after moving to newest version (run from comand line, sys.path not containing location of common modules)

Question #698112 on SikuliX changed: https://answers.launchpad.net/sikuli/+question/698112 Richard Chubb posted a new comment: Thanks for the feedback RaiMan. " I have 3 solutions: --- JYTHONPATH Set it in the environment and use the python features to extract it at runtime --- parameter add

Re: [Sikuli-driver] [Question #698112]: Windows 10: imports no longer working after moving to newest version (run from comand line, sys.path not containing location of common modules)

Question #698112 on SikuliX changed: https://answers.launchpad.net/sikuli/+question/698112 Status: Open => Answered RaiMan proposed the following answer: --- I have tried setting up the PYTHONPATH, JYTHONPATH and CLASSPATH but this had no affect. This only works, if you are running with

Re: [Sikuli-driver] [Question #697889]: How to initiate remote webdriver using selenium commands in sikuli

Question #697889 on SikuliX changed: https://answers.launchpad.net/sikuli/+question/697889 Status: Open => Expired Launchpad Janitor expired the question: This question was expired because it remained in the 'Open' state without activity for the last 15 days. -- You received this question

Re: [Sikuli-driver] [Question #698118]: my script reacts too slow when detecting the image, how to improve it?

Question #698118 on SikuliX changed: https://answers.launchpad.net/sikuli/+question/698118 RaiMan proposed the following answer: if nothing else is said, images are searched on the whole screen. The search would be faster, if you restrict the region as much as possible to the area, where you

Re: [Sikuli-driver] [Question #698118]: my script reacts too slow when detecting the image, how to improve it?

Question #698118 on SikuliX changed: https://answers.launchpad.net/sikuli/+question/698118 Status: Open => Answered Manfred Hampl proposed the following answer: see e.g. https://answers.launchpad.net/sikuli/+question/663281 make search region as small as possible around the place where you