sikuli-driver team mailing list archive

[RaiMan <question136146@xxxxxxxxxxxxxxxxxxxxx>]

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

RaiMan posted a new comment:
As long as it is "only" mouse and keyboard replay, your app must only
record clicks (together with the used button) and keyboard input. No
images needed.

One challenge will be to assure that the GUI situation is the same as at
time of recording(e.g. window size and position) or you did the
recording relative to some screen objects, that must be restored on
replay.

In case you want to use images additionally to use searches (which would
make things somewhat independent from restoring the exact window
situation), then you might need the support of the user to capture the
image in a way, that makes sense. I do not think, that this is possible
to automate without heavy image analyzing.

So you will need some hot-keys as tool for the user, to tell your app,
what might be the next action (e.g. capture needed before click).

for some of these activities, it might make sense to delegate it to
threads, to allow parallel processing. E.g. tracking mouse movement must
be threaded, to make it effective and the capturing and listening to
hotkeys and ....

But this might be going far beyond what you are thinking about in the
moment.

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