Question #191167 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/191167
RaiMan posted a new comment: @Bogdan With the current version, there is no other chance than to either run only one thread at a time, that uses the mouse or to somehow coordinate the mouse and keyboard usage among the 2 threads yourself (though this is rather complex at the script level). In the upcoming version 1.1.0 the usage of mouse and keyboard is guarded internally, so that each complex mouse operation (e.g. click) is completely processed, before another thread can use the mouse and do his click. The mouse can even be made exclusive for one thread for some time for critical operations (like for example the short processing in a popup observe-handler). Furthermore it is detected, that the mouse has been moved by an independent other thread or the user, which can be handled on request (e.g. something like a "rollback" or partial restart). Though the concurrent handling of the mouse among independent threads is a rather complex challenge, these features will make life a bit easier I guess. -- 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
