Question #252274 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/252274
Status: Open = Answered
RaiMan proposed the following answer:
not really clear, what you mean with sikulix-api.
if it is SikuliX 1.0.1: this is definitely not thread safe with respect
to the concurrent usage of mouse and keyboard in different threads and
other features like paste().
If it is SikuliX 1.1.0-BetaX: at least the mouse usage should be thread
safe now: actions like click are now synchronised, so that only one
action can be processed at one time. Moreover can the mouse usage be
reserved for one thread, so one might create something like transactions
with regard to mouse usage. Synched keyboard usage (type, write) will
follow soon.
Generally: the concurrent usage of the same SikuliX object (e.g.
regions) in different threads should work, as long as changes are only
done in one thread and the usage is somehow synched externally.
Concurrent changes might lead to unexpected results in the current
implementation.
--
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
