[1.1.0] isLockOn does not change until typing from the keyboard --- fixed 1.1.1 2016-10-31
Bug #1545428 reported by
RaiMan
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| SikuliX |
Fix Committed
|
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(
popup(msg)
type(
| Changed in sikuli: | |
| status: | New → In Progress |
| importance: | Undecided → Medium |
| assignee: | nobody → RaiMan (raimund-hocke) |
| milestone: | none → 1.1.1 |
| 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 |
| description: | updated |
Revision history for this message
| RaiMan (raimund-hocke) wrote | #1 |
| 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.
fixed the Java problem by not using the AWT Toolkit ;-)
Now the Windows API is directly accessed to get the key state.