sikuli-driver team mailing list archive

[RaiMan <question251336@xxxxxxxxxxxxxxxxxxxxx>]

Question #251336 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/251336

Description changed to:
Hi RaiMan,

I tried to run the sikuli script on Win8 32bits, but seems like it doesn't work due to the checkMousePos failures in a click action.
The same script works well on Win7 32bits. Here are the log form the console with "-d 3" options, is there a workaround for this issue?


D:\SikuliX110b2>runsikulix.cmd -d 3 -r D:\workspace_sikuli\install_pressure.sikuli
+++ running this Java
java version "1.6.0_10-rc2"
Java(TM) SE Runtime Environment (build 1.6.0_10-rc2-b32)
Java HotSpot(TM) Client VM (build 11.0-b15, mixed mode, sharing)
+++ trying to run SikuliX
+++ using: -Xms64M -Xmx512M -Dfile.encoding=UTF-8 -Dsikuli.FromCommandLine -jar
D:\SikuliX110b2\sikulix.jar -d 3 -r D:\workspace_sikuli\install_pressure.sikuli
[debug] IDE: Switching to SikuliScript with option -r, -t or -i
[debug] SikuliScript: CmdOrg: -d 3 -r D:\workspace_sikuli\install_pressure.sikul
i
[debug] Running on Java 6 (1.6.0_10-rc2-b32)
[debug] --- Sikuli parameters ---
[debug] 1: -d
[debug] 2: 3
[debug] 3: -r
[debug] 4: D:\workspace_sikuli\install_pressure.sikuli
[debug] SikuliScript: givenScriptName: D:\workspace_sikuli\install_pressure.sikuli
… more
[debug] Screen: initScreens: ScreenDevice 0 contains (0,0) --- will be used as primary
[debug] Screen: initScreens: basic initialization (1 Screen(s) found)
[debug] Screen: *** monitor configuration (primary: 0) ***
[debug] Screen: 0: S(0)[0,0 1920x1080]
[debug] Screen: *** end monitor configuration ***
[debug] Region: hover: L(960,540)@S(0)[0,0 1920x1080]
[debug] Region: hover: L(596,565)@S(0)[0,0 1920x1080]
… more
[debug] Region: find:
waiting 5.0 secs for install_main_quick_start.png to appear in R[0,0 1920x1080]@S(0)
[debug] Image: added to image list: install_main_quick_start.png
with URL: file:D:/workspace_sikuli/install_pressure.sikuli/install_main_quick_start.png
[debug] Image: loaded install_main_quick_start.png (22 KB of 64 MB (1 / 0 %) (22))
[debug] Region: find: install_main_quick_start.png has appeared
at M[1003,689 160x48]@S(S(0)[0,0 1920x1080]) S:0.85 C:1083,713 [1592/1124 msec]
[debug] Region: find: waiting 3.0 secs for install_main_quick_start.png to appear in R[0,0 1920x1080]@S(0)
[debug] Region: checkLastSeen: not there
[debug] Region: find: install_main_quick_start.png has appeared at M[1003,689 160x48]@S(S(0)[0,0 1920x1080]) S:0.85 C:1083,713 [1794/1794 msec]
[log] CLICK on L(1083,713)@S(0)[0,0 1920x1080]
[error] RobotDesktop: MouseInfo.getPointerInfo.getLocation L(596,565)@S(0)[0,0 1920x1080]
after mouseMove to L(1083,713)@S(0)[0,0 1920x1080]

this last error message tells us, that the mouse did not move to the
given location L(1083,713), but stayed at L(596,565), where it was
before script start.

The most probable cause:
SikuliX's mouse move feature (using Java Robot) is somehow blocked generally or by the frontmost application.

Possible solution:
At least on Windows, it might help, to run the SikuliX stuff as admin.
In all other cases you have to find out, why SikuliX mouse actions are blocked and then accept this or find a way to get around

-- 
You received this question notification because you are a member of
Sikuli Drivers, which is an answer contact for Sikuli.