sikuli-driver team mailing list archive

[RaiMan <rmhdevelop@xxxxxx>]

well, thanks for the code and log.

Does not shed more light on the problem though.

The same functions are used with different images in both cases.

... and at the beginning of onMouseHoverImageMap the correct x-value for
automationTesterCurrentScreen is reported.

... but when stepping down one line later into
automationTesterCurrentScreen.hover(new Pattern(patternStringPath).similar(new Float(0.4)));

the shit happens, without any intermediate action, that might be
responsible for the change.

So the problem must have been produced before.
The last find in testOnMouseHoverOrthogonalLayout fails and triggers your function TSAutomationUtils.getScreenShot.

- please paste this code?
- what happens, if you comment this line out, so it is not called?

-- 
You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.
https://bugs.launchpad.net/bugs/1386862

Title:
  [1.1.0] OS X 10.10: Location: outside any screen in multi-monitor
  setup

Status in Sikuli:
  In Progress

Bug description:
  Sikulix API  Version: 1.1.0
  Yosemite 64 bits


  I'm developing a solution on Java with Sikuli, with two monitors, on Mac OS after I updated to Yosemite I began to get the next errors message:
  error] Location: outside any screen (-2560, 0) - subsequent actions might not work as expected
  [error] Location: outside any screen (-2560, 0) - subsequent actions might not work as expected
  [error] Location: outside any screen (-1484, 153) - subsequent actions might not work as expected

  I've make changes to Display settings and update to Java 1.8 JDK and JRE
  I use this method to get the Screen ID:

  public static int getCurrentScreenId(Pattern pattern) throws Exception
  	{
  		int result = 0;

  		for (int i = 0; i <= 1; i++)
  		{
  			System.out.println("Try number " + i);
  			if (new Screen(i).exists(pattern) != null)
  			{
  				System.out.println("Searching on Screen: " + i);
  				result = i;
  				System.out.println("Screen founded =" + result);

  			}
  			else
  			{
  				continue;
  			}

  		}
  		return result;
  	}
  NOTE: on Yosemite the screen 0 (default) is the monitor connected to the machine, if you unplugged the monitor then the screen(0) is the screen machine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/sikuli/+bug/1386862/+subscriptions