sikuli-driver team mailing list archive

[RaiMan <question661348@xxxxxxxxxxxxxxxxxxxxx>]

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

    Status: Open => Answered

RaiMan proposed the following answer:
--- None of these settings make really sense:
            Settings.MoveMouseDelay = 0.1 # 0 would be the value, to switch of the mouse move animation
            Settings.DelayBeforeMouseDown = 0.1 # only relevant for dragDrop, no effect with click
            Settings.ClickDelay = 0.1 # time between down and up for click, standard is 0 which normally works.

--- click using a thread:
not needed with SikuliX 1.1.1+, since internally mouse actions are globally synchronized

--- extended delay
Internally SikuliX uses the Java AWT Robot class to handle mouse actions (Button up/down and move). All higher level mouse actions are composed based on these Robot features.
The error message comes up, when inside the Robot a feature like ButtonDown does not come back after a maximum delay (standard 1 second). This extended delay is not created by any SikuliX feature, but is completely in the layer between the Robot and the system mouse handling.

Since you are automating a game, it might well be, that the game engine
is aware of the fact that the mouse actions are non-human and hence
interferes the mouse handling with some delay, which seems probable
looking at the continuous increase of the delay.

You might try, to implement your central click function using
mouseDown() and mouseUp() with surrounding and intermediate short waits,
that are randomly generated. This may help, to avoid being detected as a
non-human.

-- 
You received this question notification because your team Sikuli Drivers
is subscribed to the question.