Sikuli mouse controls are blocked?

Asked by Richard Loong on 2017-11-27

I've been trying to run a Sikuli script which worked perfectly fine on another PC, but seems to have issues when running on my Microsoft Surface Pro 4. This is the log from the Command Prompt while the script runs. This is the part which seems relevant to Sikuli, I excluded the other parts which were only relevant to the script I was running.

[log] App.focus: [3544:Chrome]
[error] RobotDesktop: checkMousePosition: should be L(485,184)@S(0)[0,0 2736x1824]
but after move is L(578,278)@S(0)[0,0 2736x1824]
Possible cause in case you did not touch the mouse while script was running:
 Mouse actions are blocked generally or by the frontmost application.
You might try to run the SikuliX stuff as admin.
[error] RobotDesktop: checkMousePosition: should be L(589,392)@S(0)[0,0 2736x1824]
but after move is L(590,374)@S(0)[0,0 2736x1824]
Possible cause in case you did not touch the mouse while script was running:
 Mouse actions are blocked generally or by the frontmost application.
You might try to run the SikuliX stuff as admin.
[log] App.focus: [3544:Chrome]
[log] TYPE "#ESC."

It seems to be suggesting that I run SikuliX as an administrator, but how do I go about running a jar as an administrator? Also, it worked fine on my other PC without any administrator permissions.

When I run the script, the mouse cursor does move on its own, however it's jittery and stops after a few seconds.

Question information

Language:
English Edit question
Status:
Answered
For:
Sikuli Edit question
Assignee:
No assignee Edit question
Last query:
2017-11-27
Last reply:
2017-11-27
RaiMan (raimund-hocke) said : #1

I guess it is the same problem as with latest Windows 10 on PC's:
bug 1730645

LOL, something wrong under the surface ;-)

I have no idea currently about this behavior and no solution.

Richard Loong (spawnage) said : #2

I'm not really sure that it's a Windows 10 issue since my other PC runs on Windows 10 but runs the same script perfectly fine.

RaiMan (raimund-hocke) said : #3

I can confirm, that it also works fine on my Windows 10 latest build on desktop machine.

But definitely there are problems on some machines having this Windows 10 latest build (and before the update it worked).

My guess is that the problem depends on a specific hardware/software/driver combination, that we both do not have on our desktop machines - and many other people seem to work without problems, since I had only 2 complaints until now and you are the 3rd with your Surface machine.

I am sorry for that, but as mentioned: ???????????????????

Can you help with this problem?

Provide an answer of your own, or ask Richard Loong for more information if necessary.

To post a message you must log in.