New question #683754 on Sikuli: https://answers.launchpad.net/sikuli/+question/683754
Hello All, I've been using sikuliapi for several months (in-house java application with sikulixapi.jar) and everything has been working flawlessly. Usually, the sikulix app runs inside a virtual machine (in this case, Oracle Virtualbox is used) with Windows 10 as guest, while the host is a Linux system. However, recemtly I've been doing several tests with multiple Win10 VMs, running on the aforementioned linux host, each one running my silulix app concurrently. Well, sure, it didn't work. Thing is, if I've figured this out correctly, that when multiple VMs (each of them running a sikulix app) try to capture the mouse _simultaneously_ , sikulix will throw the famous "mouse should be at ... but it is at .... might try to run sikulix stuff as administrator..." This behaviour makes sense to me, and I understand this isn't even sikulix's fault, but instead it's due to the fact that a host system has a single "mouse resource" which must share between all of his VMs; considering the fact that an human user cannot possibly click on two VMs at the same time, there's no problem with such a limitation. Enter multiple sikulix instances running in parallel VMS, and obviously everything is blown out of the water. While I do understand that this could be an inherent limitation from how Level-2 hypervisors work (i.e., perhaps what I am trying to do simply can not be done), I'm posting this question here because perhaps someone has found a similar scenario before, and could lend me a hand or give me a suggestion on how this [somewhat complex] scenario could get solved. thanks for your time, Jose -- You received this question notification because your team Sikuli Drivers 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
