sikuli-driver team mailing list archive

[omearam <1730645@xxxxxxxxxxxxxxxxxx>]

Ok using W10, Java 11 & IDE 1.1.3 and it has fixed the issue but seeing
this IDE output on startup, does seem to affect IDE behaviour in
general.

C:\WINDOWS\system32>c:\temp\silkuli\runsikulix.cmd
+++ running this Java
java version "11.0.1" 2018-10-16 LTS
Java(TM) SE Runtime Environment 18.9 (build 11.0.1+13-LTS)
Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.1+13-LTS, mixed mode)
+++ trying to run SikuliX
+++ using: -Xms64M -Xmx512M -Dfile.encoding=UTF-8 -Dsikuli.FromCommandLine -jar c:\temp\silkuli\sikulix.jar
[error] RunTimeINIT: *** BE AWARE: Running on Java 8+ *** Please report problems ***
[info] HotkeyManager: add Capture Hotkey:  NUM LOCK (144, 0)
[info] HotkeyManager: add Abort Hotkey: ALT+SHIFT C (67, 9)
Exception in thread "Thread-2" java.lang.UnsatisfiedLinkError: C:\Users\omearam\AppData\Local\Temp\jna--1294165632\jna12381214207587878606.dll: Can't find dependent libraries
        at java.base/java.lang.ClassLoader$NativeLibrary.load0(Native Method)
        at java.base/java.lang.ClassLoader$NativeLibrary.load(ClassLoader.java:2430)
        at java.base/java.lang.ClassLoader$NativeLibrary.loadLibrary(ClassLoader.java:2487)
        at java.base/java.lang.ClassLoader.loadLibrary0(ClassLoader.java:2684)
        at java.base/java.lang.ClassLoader.loadLibrary(ClassLoader.java:2617)
        at java.base/java.lang.Runtime.load0(Runtime.java:767)
        at java.base/java.lang.System.load(System.java:1831)
        at com.sun.jna.Native.loadNativeDispatchLibraryFromClasspath(Native.java:851)
        at com.sun.jna.Native.loadNativeDispatchLibrary(Native.java:826)
        at com.sun.jna.Native.<clinit>(Native.java:140)
        at com.sun.jna.Pointer.<clinit>(Pointer.java:41)
        at com.sun.jna.Structure.<clinit>(Structure.java:2078)
        at com.tulskiy.keymaster.windows.WindowsProvider$1.run(WindowsProvider.java:55)
        at java.base/java.lang.Thread.run(Thread.java:834)
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.python.core.PySystemState (file:/C:/temp/silkuli/sikulix.jar) to method java.io.Console.encoding()
WARNING: Please consider reporting this to the maintainers of org.python.core.PySystemState
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release

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

Title:
  [1.1.4] Windows 10: Move mouse for click not working since new JRE and
  Windows update with Java 8 and HiDPI --- workaround Java 9 and scaling
  100% OR try with Java 11

Status in Sikuli:
  In Progress

Bug description:
  ********************* Java problem
  seems to be related to a problem with HiDPI and scaled monitor setups
  https://bugs.openjdk.java.net/browse/JDK-8196030

  The problem seems to exist with Java 8 not supporting HiDPI.

  Using Java 9 or 10 on HiDPI systems with a scaling of 100% seems to
  work

  Using Java 11 these experiences are reported:
  early build of jdk 11 and sikuli 1.1.4 is working good for hidpi, but still we observed few issues mentioned below:

  1) Sikuli scripts written using 4k (3840*2160) with recommended
  scaling (300%) is working only for the same recommended settings. If
  we change the resolution to 2K or 1080P or below , and also if we
  change scaling, scripts are failing

  2) Sikuli scripts written on 2k (2560*1600) with recomended scaling (200%) is working for for resolutions below 2k like 800*600 to 1920*1080 (Downscaling is working with this) and for 4k it is not working (Upscaling is not working) 
  -------------------------------------------------

  wondering if anyone else is seeing this.

  I install the latest big update for Windows this morning and also
  accepted an update to the latest JRE.

  Now my when Sikuli moves the mouse to click on a match it doesn't land
  on the coordinates.   It even recognizes that it missed and has an
  error message saying it tried to move the mouse to (x, y), but landed
  on (p, q) instead.

  Any idea what is happening and how to fix it?

  Thanks!

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