sikuli-driver team mailing list archive

[RaiMan <sikulix@xxxxxxxxxxx>]

Public bug reported:

********************** the observed behaviour

I have four monitors. If I initiate Sikuli from monitor 1, everything
works. If I initiate Sikuli from any of the other monitors, I get the
errors I posted above and the IDE never starts. You can see that the
exception is within the mouse initialization. It doesn't matter if I'm
launching Sikuli from the command line or by double-clicking the jar
file. I have to launch from monitor 1 to use it.

I can put the IDE on any monitor once it is running. The matching
preview function can find an image on any monitor. However, when Sikuli
runs, it only finds images on monitor 1.

-------------------------------------------------------------------------------------------------------------
I deleted an older version of SikuliX and copied the latest jython-standalone-2.7.1.jar, sikulix.jar, and sikulixapi.jar. I've installed JRE and then JDK 8.0.2 and rebooted my machine. When I click the jython and api jars, I get a wait cursor for a few seconds, and then nothing. When I click on the sikulix.jar, I get an error that Neither Jython nor Jruby are available, so the IDE won't open.
I've spent about 2 hours trying various installs of Java and reading google and this forum, and can't find anything helpful.
I'm on Windows 10 and have run Sikuli before without issue. Should I just go back to the old version, or is there something I can do?

Is there an order of operations when launching all the jar files? Also,
it's really confusing on the Java site as to which version to download -
JRE, JDK, SE, etc. Which should I download? I use Jython in the IDE,
which is why I though JDK would be correct.

** Affects: sikuli
     Importance: Medium
     Assignee: RaiMan (raimund-hocke)
         Status: In Progress

** Changed in: sikuli
       Status: New => In Progress

** Changed in: sikuli
   Importance: Undecided => Medium

** Changed in: sikuli
     Assignee: (unassigned) => RaiMan (raimund-hocke)

** Changed in: sikuli
    Milestone: None => 1.1.4

-- 
You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.
https://bugs.launchpad.net/bugs/1820820

Title:
  [1.1.4] Windows: multi-monitor environment: SikuliX behaviour depends
  on the monitor it is started on

Status in Sikuli:
  In Progress

Bug description:
  ********************** the observed behaviour

  I have four monitors. If I initiate Sikuli from monitor 1, everything
  works. If I initiate Sikuli from any of the other monitors, I get the
  errors I posted above and the IDE never starts. You can see that the
  exception is within the mouse initialization. It doesn't matter if I'm
  launching Sikuli from the command line or by double-clicking the jar
  file. I have to launch from monitor 1 to use it.

  I can put the IDE on any monitor once it is running. The matching
  preview function can find an image on any monitor. However, when
  Sikuli runs, it only finds images on monitor 1.

  -------------------------------------------------------------------------------------------------------------
  I deleted an older version of SikuliX and copied the latest jython-standalone-2.7.1.jar, sikulix.jar, and sikulixapi.jar. I've installed JRE and then JDK 8.0.2 and rebooted my machine. When I click the jython and api jars, I get a wait cursor for a few seconds, and then nothing. When I click on the sikulix.jar, I get an error that Neither Jython nor Jruby are available, so the IDE won't open.
  I've spent about 2 hours trying various installs of Java and reading google and this forum, and can't find anything helpful.
  I'm on Windows 10 and have run Sikuli before without issue. Should I just go back to the old version, or is there something I can do?

  Is there an order of operations when launching all the jar files?
  Also, it's really confusing on the Java site as to which version to
  download - JRE, JDK, SE, etc. Which should I download? I use Jython in
  the IDE, which is why I though JDK would be correct.

To manage notifications about this bug go to:
https://bugs.launchpad.net/sikuli/+bug/1820820/+subscriptions