Question #254582 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/254582
Status: Open => Answered
RaiMan proposed the following answer:
ok, understood.
There is no general solution for these "asynchronous" (means: cannot be
foreseen in the sense of a workflow) popups, because:
- not all popups have the same visual aspects, only some "families" (e.g. same
icon or other visual aspects)
- since mouse and keyboard usage have to be coordinated, the concrete solution
depends on what Sikuli workflows run in parallel
The most general solution is to run an observe in background and handle the
specific poup, when it appears. one observe might handle more then one event
and you might even dispatch more than one observe.
Beginning with version 1.1.0 at least the mouse usage can be synchronized
between the main workflow thread and the dispatched observers running in their
own threads.
Until including 1.0.1 especially the mouse usage might be mangled. And
generally the main workflow might run into a problem, before the popup
is handled (this timing aspect is very hard to attack).
As generally for Sikuli, the more the observation can be restricted to specific
areas on the screen, the less cpu load.
Using ObserveScanRate one can control how often observe checks the appearances.
--
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 : [email protected]
Unsubscribe : https://launchpad.net/~sikuli-driver
More help : https://help.launchpad.net/ListHelp
