sikuli-driver team mailing list archive
-
sikuli-driver team
-
Mailing list archive
-
Message #31314
[Bug 1436521] Re: [1.1.0] Clicks on secondary monitor after finding image on primary monitor
should work with nightly 20150327+
** Changed in: sikuli
Status: New => Fix Committed
** Changed in: sikuli
Importance: Undecided => Critical
** Changed in: sikuli
Assignee: (unassigned) => RaiMan (raimund-hocke)
** Changed in: sikuli
Milestone: None => 1.1.0
** Summary changed:
- [1.1.0] Clicks on secondary monitor after finding image on primary monitor
+ [1.1.0] Clicks on secondary monitor after finding image on primary monitor --- fixed 20150327
--
You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.
https://bugs.launchpad.net/bugs/1436521
Title:
[1.1.0] Clicks on secondary monitor after finding image on primary
monitor --- fixed 20150327
Status in Sikuli:
Fix Committed
Bug description:
1.1.0 3/25 nightly and 3/24 nightly.
Win7 32-bit
I'm seeing 2 behaviors that I cannot consistently reproduce in 1.1.0, but works fine in 1.0.1.
Sikuli will find the image on the primary monitor, and then I see it move the mouse to my secondary monitor and click (clicking the wrong spot).
I'm using:
wait(imgA)
click(imgA)
It's either that or it will click on the primary monitor, but slightly
below the image.
If I move the browser to the secondary monitor, Sikuli will fail to
find the image. Once it breaks, even if I restart sikulix.jar it
doesn't fix it.
If I open the same script in 1.0.1, it will work.
To manage notifications about this bug go to:
https://bugs.launchpad.net/sikuli/+bug/1436521/+subscriptions
References