[1.1.0] isLockOn does not change until typing from the keyboard --- fixed 1.1.1 2016-10-31

Bug #1545428 reported by RaiMan on 2016-02-14
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Sikuli
Critical
RaiMan

Bug Description

I am sure this behavior by using the following code.
When I click the OK button at the pop-up window, status does not change.
When I type Enter-key at the pop-up window, status will change.
(I tested on Windows7, Java 1.8.0, SikuliX1.1.0 .)

while True:
    msg = "status:%s" % Env.isLockOn(Key.NUM_LOCK)
    popup(msg)
    type(Key.NUM_LOCK)

RaiMan (raimund-hocke) on 2016-02-14
Changed in sikuli:
status: New → In Progress
importance: Undecided → Medium
assignee: nobody → RaiMan (raimund-hocke)
milestone: none → 1.1.1
RaiMan (raimund-hocke) on 2016-10-28
Changed in sikuli:
status: In Progress → Fix Committed
milestone: 1.1.1 → 2.0.0
summary: - [1.1.0] isLockOn does not change until typing from the keyboard
+ [1.1.0] isLockOn does not change until typing from the keyboard --- will
+ only be fixed in version 2
RaiMan (raimund-hocke) on 2016-10-28
description: updated
RaiMan (raimund-hocke) wrote :

fixed the Java problem by not using the AWT Toolkit ;-)
Now the Windows API is directly accessed to get the key state.

summary: - [1.1.0] isLockOn does not change until typing from the keyboard --- will
- only be fixed in version 2
+ [1.1.0] isLockOn does not change until typing from the keyboard ---
+ fixed 1.1.1 2016-10-31
description: updated
Changed in sikuli:
importance: Medium → Critical
milestone: 2.0.0 → 1.1.1
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers