Re: [Sikuli-driver] [Question #265660]: My imports stopped working when I moved to newest version (sys.path issue?)

2015-04-23 Thread forrest
Question #265660 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/265660 Status: Answered = Open forrest is still having a problem: IF I set JYTHONPATH then I cannot even get the IDE or the interactive jython to start - both have same error NameError: name

Re: [Sikuli-driver] [Question #265660]: My imports stopped working when I moved to newest version (sys.path issue?)

2015-04-23 Thread forrest
Question #265660 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/265660 Status: Needs information = Open forrest gave more information on the question: Re: ...could you please... #6 == Fresh Win Command Console == Microsoft

[Sikuli-driver] [Question #265660]: My imports stopped working when I moved to newest version (sys.path issue?)

2015-04-21 Thread forrest
files so that imports work for free -- like before --or-- 2) I can provide path info on the runsikulix.cmd command line Thank You forrest -- You received this question notification because you are a member of Sikuli Drivers, which is an answer contact for Sikuli

Re: [Sikuli-driver] [Question #265660]: My imports stopped working when I moved to newest version (sys.path issue?)

2015-04-22 Thread forrest
Question #265660 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/265660 Status: Answered = Open forrest is still having a problem: Thank you both for the timely response. Perhaps I am missing something but I don't see an answer that works in either of the posts. Given

Re: [Sikuli-driver] [Question #265660]: [1.1.0] Windows: My imports stopped working when I moved to newest version (sys.path issue?)

2015-04-24 Thread forrest
Question #265660 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/265660 Status: Answered = Open forrest is still having a problem: Thank you. Is there a way that I can know when this gets fixed ? That is, what should I look for either on the board or release notes, etc

Re: [Sikuli-driver] [Question #266141]: [1.1.0] Jython-2.7-rc3: Subclassing Region: with __init__ the java level constructors not used with super()__init__(), leaving Region empty --- workaround

2015-04-30 Thread forrest
Question #266141 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/266141 Status: Answered = Open forrest is still having a problem: Yes, that worked for me. Jython adds another fun dimension to the challenge of SWD... Thank You for your attention to this. Much appreciated

[Sikuli-driver] [Question #266141]: Extending Region breaks when I move to new Sikuli

2015-04-29 Thread forrest
New question #266141 on Sikuli: https://answers.launchpad.net/sikuli/+question/266141 Installed nightly sikulixsetup-1.1.0-20150427.231036-54-forsetup, and my old code is breaking when I try to highlight a class that extends Region. The code worked fine with Sikuli from Dec 2014 and recently

Re: [Sikuli-driver] [Question #266141]: [1.1.0] Jython-2.7-rc3: Subclassing Region: with __init__ the java level constructors not used with super()__init__(), leaving Region empty --- workaround

2015-04-30 Thread forrest
Question #266141 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/266141 Status: Open = Solved forrest 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 #265409]: FIXED: Unable to debug simple Sikuli in Eclipse/Jython

2015-04-18 Thread forrest
Question #265409 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/265409 forrest posted a new comment: Blessings2Ewe -Original Message- From: boun...@canonical.com [mailto:boun...@canonical.com] On Behalf Of RaiMan Sent: Saturday, April 18, 2015 9:52 AM To: Forrest

Re: [Sikuli-driver] [Question #265409]: FIXED: Unable to debug simple Sikuli in Eclipse/Jython

2015-04-18 Thread forrest
Question #265409 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/265409 Summary changed to: FIXED: Unable to debug simple Sikuli in Eclipse/Jython Description changed to: I wish I could have deleted this request, but... I wiped out all vestiges of sikuli and

[Sikuli-driver] [Question #265409]: Unable to debug simple Sikuli in Eclipse/Jython

2015-04-17 Thread forrest
New question #265409 on Sikuli: https://answers.launchpad.net/sikuli/+question/265409 I have been completely unsuccessful trying to get Eclipse to debug with Jython for the simplest script. I have started with a fresh Eclipse Luna Installed PyDev and JYthon 2.54rc1 and followed

[Sikuli-driver] [Question #670801]: Unable to use Finder with Jython where Screen works OK

2018-07-10 Thread forrest
I have also tried findAll() as well as find(). Any ideas what the issue may be? Many thanks, forrest -- You received this question notification because your team Sikuli Drivers is an answer contact for Sikuli. ___ Mailing list: https://launchpad.net

Re: [Sikuli-driver] [Question #670801]: Unable to use Finder with Jython where Screen works OK

2018-07-12 Thread forrest
Question #670801 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/670801 Status: Answered => Open forrest is still having a problem: Yes, I would expect that but it does not. Here is same code with prints to demonstrate: import org.sikuli.script.SikulixForJyt

[Sikuli-driver] [Question #691091]: Fresh Ubuntu install on VM and SikuliX IDE will not start

2020-06-02 Thread Matthew Forrest
New question #691091 on Sikuli: https://answers.launchpad.net/sikuli/+question/691091 Hi, I have a fresh Ubuntu install on a VM. I've tried to put Sikuli onto this VM and launch the IDE but it will not start. If I double click the jar file I briefly see a popup that the IDE is starting and

Re: [Sikuli-driver] [Question #691091]: Fresh Ubuntu install on VM and SikuliX IDE will not start

2020-06-04 Thread Matthew Forrest
Question #691091 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/691091 Status: Answered => Solved Matthew Forrest confirmed that the question is solved: For future readers, I solved by uninstalling openjdk-8-jdk and installing openjdk-11-jdk Still not sure what the is