sikuli-driver team mailing list archive

[angelo <angelo@xxxxxxxxxxxxxxx>]

Public bug reported:

public class SikuliTest {

	public static void main(String[] args) {
		try {
			Region searchRegion = new Screen();
			searchRegion.setObserveScanRate(0.1f);

			Long startingTime = System.currentTimeMillis();
			Match match = searchRegion.wait("cancel_button.png",
					Constants.FOREVER);
			match.click();
			System.out.println("Thread1: "
					+ (System.currentTimeMillis() - startingTime) + "ms");

		} catch (FindFailed e) {
			// TODO Auto-generated catch block
			e.printStackTrace();
		}
	}
}

If I bring the desired target to the screen after the program started I
get always a similar reaction time.

[log] CLICK on L(280,194)@S(0)[0,0 2560x1440]
Thread1: 4157ms

With 0.1f I would have expected that Sikulix  searches every 10 seconds
with a lower CPU usage, but it is always the same. When setting the
observe scan rate via the global settings, it behaves as expected.

** 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/1540233

Title:
  Region.setObserveScanRate(float observeScanRate) without any function

Status in Sikuli:
  New

Bug description:
  public class SikuliTest {

  	public static void main(String[] args) {
  		try {
  			Region searchRegion = new Screen();
  			searchRegion.setObserveScanRate(0.1f);

  			Long startingTime = System.currentTimeMillis();
  			Match match = searchRegion.wait("cancel_button.png",
  					Constants.FOREVER);
  			match.click();
  			System.out.println("Thread1: "
  					+ (System.currentTimeMillis() - startingTime) + "ms");

  		} catch (FindFailed e) {
  			// TODO Auto-generated catch block
  			e.printStackTrace();
  		}
  	}
  }

  If I bring the desired target to the screen after the program started
  I get always a similar reaction time.

  [log] CLICK on L(280,194)@S(0)[0,0 2560x1440]
  Thread1: 4157ms

  With 0.1f I would have expected that Sikulix  searches every 10
  seconds with a lower CPU usage, but it is always the same. When
  setting the observe scan rate via the global settings, it behaves as
  expected.

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