[2.0.4] some keyboard commands not recognized by certain programs
Bug #1891391 reported by
Zed
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
SikuliX |
Opinion
|
Undecided
|
RaiMan |
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:/
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.
Changed in sikuli: | |
status: | New → Opinion |
importance: | Undecided → Medium |
assignee: | nobody → RaiMan (raimund-hocke) |
milestone: | none → 2.0.5 |
summary: |
- In SikuliX 2.0.4, some keyboard commands not recognized by certain - programs + [2.0.4] some keyboard commands not recognized by certain programs |
Changed in sikuli: | |
importance: | Medium → Undecided |
To post a comment you must log in.
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 AutoDetectKeybo ardLayout = False
Settings.
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.