sikuli-driver team mailing list archive

[RaiMan <1891391@xxxxxxxxxxxxxxxxxx>]

SikuliX from beginning internally uses Java AWT Robot, to issue key
strokes.

With version 2.0.x we introduced a feature for Windows to automatically
detect the keyboard layout (in 1.1.x this was restricted to the US
layout by Java) and now issue the key strokes using the Windows native
API.

This feature is switched on in the standard. It can be switched off using 
Settings.AutoDetectKeyboardLayout = False

which means: fall back to the Java AWT Robot usage with the restriction
to the US layout.

I tested on Windows 10 with a NotePad++ window: all mentioned keys work
as expected and in both Settings variants (Win10-64(2004), Java 11)
(German keyboard layout).

This means, SikuliX sends the keys correctly to Windows.
What certain apps are doing with that simulated keys and how they get the key info is beyond the scope of SikuliX.

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

Title:
  [2.0.4] some keyboard commands not recognized by certain programs

Status in Sikuli:
  Opinion

Bug description:
  It looks like for some Windows applications, certain navigation keys (Key.PAGE_UP, Key.PAGE_DOWN, Key.HOME, and Key.END) are not being recognized properly on SikuliX 2.0.x versions.
   
  For example, if you use this keyboard test program https://www.passmark.com/products/keytest/ and trying to use Sikuli to trigger test those keys, they seemingly get ignored. I used 2.0.4 to test but also tried previous 2.0.x versions and they seem to have the same result.

  If I go back to the old 1.1.3 version, those same commands appear to
  work fine and appropriate key code is shown.

  For testing, I used Windows 10 1909 64-bit, and both Java 8 and Java
  11.

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