[1.1.0] ObserveScanRate without any function
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
SikuliX |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Hi,
as far as I understood from the documentation the properties WaitScanRate and ObserveScanRate should be the same function. But ObserveScanRate does not change anything in my case but WaitScanRate behaves as expected. Even worse is that only the ObserveScanRate can be set for a region.
Here is my test.
public class SikuliTest {
public static void main(String[] args) {
try {
// Settings.
// Settings.
Region searchRegion = new Screen();
searchRegion
Long startingTime = System.
Match match = searchRegion.
Constants.
match.click();
System.
+ (System.
} catch (FindFailed e) {
// TODO Auto-generated catch block
e.printStack
}
}
}
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. It has also no effect if I set the observe scan rate via the global settings. Only Settings.
Edited on 03-02-2016, when I realized the difference between WaitScanRate and ObserveScanRate.
description: | updated |
description: | updated |
summary: |
- Region.setObserveScanRate(float observeScanRate) without any function + ObserveScanRate without any function |
summary: |
- ObserveScanRate without any function + ObserveScanRate vs. WaitScanRate |
description: | updated |
description: | updated |
summary: |
- ObserveScanRate vs. WaitScanRate + [1.1.0] ObserveScanRate vs. WaitScanRate |
summary: |
- [1.1.0] ObserveScanRate vs. WaitScanRate + [1.1.0] ObserveScanRate without any function |
Found the answer here: https:/ /answers. launchpad. net/sikuli/ +question/ 214163