sikuli-driver team mailing list archive

[RaiMan <question230237@xxxxxxxxxxxxxxxxxxxxx>]

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

    Status: Open => Answered

RaiMan proposed the following answer:
This is one of the major problems with Sikuli:
You do not get any feedback, wether a click was performed in real.

There are some known situations, where it might be possible, that a click is processed, but does not happen.
The most often reason is timing: the GUI for some reason is not yet ready, to accept a click.
Typical are sequences like
click(...) # get to an entry field
type(...) # type something
click(...) # click a button

even a short (e.g. wait(0.5) ) might stabilize the situation.

(this was one of the reasons, why Sean implemented the mouse move
animation: to give the GUI some time to prepare for the next click, but
this sometimes does not help either)

A button that changes on hover should not be the problem, since normally
the search for the button was done in a situation before, where the
mouse pointer was somewhere else on the screen.

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