sikuli-driver team mailing list archive

[domocoma <1436521@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

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.

** Affects: sikuli
     Importance: Undecided
         Status: New

-- 
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:
  Clicks on secondary monitor after finding image on primary monitor

Status in Sikuli:
  New

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