Question #240001 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/240001
Status: Open => Answered
RaiMan proposed the following answer:
ok, understood.
Since you say it works as expected with admin rights (supposing you run
it with "run as admin"), then there should not be any programmatical
problems ( like FindFailed, wrong imports, ... ).
And running normally does not produce any error messages as well
(especially FindFailed problems), as I understand, but clicks do not act
as expected.
You should run normally but with slow motion (yellow button in IDE or
setShowActions(True) at beginning of main script when running from
command line). So you can check better, if and where Sikuli intends to
click.
The only possibility left is, that the parts of the screen that you want to
click is somehow restricted (like for mmc-console windows).
Access right problems with the file system should not be the cause, since this
should lead to FindFailed exceptions.
When using version 1.0.1, running from command line with -d 3 could
reveal some more debugging information.
no more ideas, sorry.
--
You received this question notification because you are a member of
Sikuli Drivers, which is an answer contact for Sikuli.
_______________________________________________
Mailing list: https://launchpad.net/~sikuli-driver
Post to : sikuli-driver@lists.launchpad.net
Unsubscribe : https://launchpad.net/~sikuli-driver
More help : https://help.launchpad.net/ListHelp
