[Sikuli-driver] [Bug 1409098] Re: findAll limited to 100 matches
@skeets Yep, that problem is builtin with findAll(): in some margin around a match another match will not be looked for (speed), which makes sense for non-solid images. If an image can be found more than once in a region, it is not predictable (due to the underlying OpenCV feature matchTemplate()) in what sequence they will be found. For solid images these 2 effects together lead to your experience. Even when looking for a solid image in a larger solid region, the match location is not predictable and might not be reproducible. There will be no change for that behaviour in version 1. I am not sure wether it changes the situation, but did you try with Pattern(image).exact() instead of just image? -- You received this bug notification because you are a member of Sikuli Drivers, which is subscribed to Sikuli. https://bugs.launchpad.net/bugs/1409098 Title: findAll limited to 100 matches Status in Sikuli: In Progress Bug description: Calls to findAll seem to report at most 100 matches., silently discarding any further matches. Suggest findAll be configurable to specify the maximum number of matches, even if the default is 100, in the same way that similarity defaults to 0.7 but can be configured. Also suggest that if the max is exceeded, an exception is thrown so that missing matches can be spotted easily To manage notifications about this bug go to: https://bugs.launchpad.net/sikuli/+bug/1409098/+subscriptions ___ 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
Re: [Sikuli-driver] [Question #661603]: Set tolerance in click(image)
Question #661603 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/661603
Status: Answered => Open
Max is still having a problem:
thanks for the tips!
I was able to do it using pattern as you suggested with the following
code:
my_image = find(Pattern("1513067174539.png").similar(0.5))
click(my_image)
Then I tried to insert exsist function since I don't know a priori if
the image is present and I don't want that if the find fails the program
stops, but the script crashed.
while true
my_image = find(Pattern("1513067174539.png").similar(0.5))
if exists(my_image):
click(my_image)
else:
sleep(5)
type("t", KeyModifier.CTRL)
How can I solve this problem? Is it possible to use a mach object
obtained by find() inside exsist()???
--
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 : sikuli-driver@lists.launchpad.net
Unsubscribe : https://launchpad.net/~sikuli-driver
More help : https://help.launchpad.net/ListHelp
Re: [Sikuli-driver] [Question #661603]: Set tolerance in click(image)
Question #661603 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/661603
Status: Open => Answered
RaiMan proposed the following answer:
exists is the same as find, but does not stop with FindFailed in case of
not found.
while true
my_image = exists(Pattern("1513067174539.png").similar(0.5))
if my_image:
click(my_image)
else:
sleep(5)
type("t", KeyModifier.CTRL)
BTW: already know the docs
http://sikulix-2014.readthedocs.io/en/latest/index.html
alternatively:
while true
if exists(Pattern("1513067174539.png").similar(0.5)):
click()
# click(getLastMatch()) #with versions before 1.1.1
else:
sleep(5)
type("t", KeyModifier.CTRL)
one more thing:
Your loop runs forever.
So it is only interruptible by brute force.
think about integrating some leave condition
if someCondition:
break
see faq 1437
--
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 : sikuli-driver@lists.launchpad.net
Unsubscribe : https://launchpad.net/~sikuli-driver
More help : https://help.launchpad.net/ListHelp
Re: [Sikuli-driver] [Question #661603]: Set tolerance in click(image)
Question #661603 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/661603 Status: Answered => Solved Max confirmed that the question is solved: Thanks RaiMan, that solved my question. -- 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 : sikuli-driver@lists.launchpad.net Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
[Sikuli-driver] [Bug 1409098] Re: findAll limited to 100 matches
OK thanks for the info and suggestion!! Makes more sense now. For us, we need to be able to find the expected (child) image at the expected coordinates within the parent image for our test to pass. Those expected coordinates may not always be at 0,0 within the parent image. So in order to find the child image (the blank image in question), we thought we needed to use the findall method since in this case the child image can be found in many places within our parent image. So we loop through all of the findall matches testing the match coordinates against our expected coordinates. So it doesn't seem to me that we could use your suggestion if I understand correctly? Unfortunately we can't scale down our parent image any further or else it will not be unique enough on our screen. BUT we can update our "blank" image to not be blank anymore. We are testing a field to see if it has an icon or not and that field has a neighbor field that is never blank so think we can also get around this issue with a bigger child image that includes part of the neighbor field. -- You received this bug notification because you are a member of Sikuli Drivers, which is subscribed to Sikuli. https://bugs.launchpad.net/bugs/1409098 Title: findAll limited to 100 matches Status in Sikuli: In Progress Bug description: Calls to findAll seem to report at most 100 matches., silently discarding any further matches. Suggest findAll be configurable to specify the maximum number of matches, even if the default is 100, in the same way that similarity defaults to 0.7 but can be configured. Also suggest that if the max is exceeded, an exception is thrown so that missing matches can be spotted easily To manage notifications about this bug go to: https://bugs.launchpad.net/sikuli/+bug/1409098/+subscriptions ___ 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
Re: [Sikuli-driver] [Question #661621]: Using Sikuli in multiple RDP connections
Question #661621 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/661621 Description changed to: Hi there, First of all, thank you so much for all the work you do. Sikuli is the great tool, and it is really great you support it and move it forward. With Sikuli, you help lots of people to solve issues they face in automation. My question seems to be a little dummy in some sense, but it is quite important at the same time. It is a dummy because I don't understand in the full extent how Sikuli emulates mouse clicks and keyboard typing, and it is important because we rely on Sikuli heavily. Prehistory: So we are using Sikuli a lot in our automated tests. Here is how it looks like: there are some Windows machines (aka dispatchers) where automated tests run. On each dispatcher, tests start on schedule (by a Windows scheduled tasks), and tests on these dispatchers run simultaneously. For Sikuli to work on each of those dispatchers, you need a Windows user to be logged in. So from my desktop, I have RDP sessions opened to each of those dispatchers. I open these sessions either via mstsc.exe (a standard Windows RDP connection), or with Microsoft Remote Desktop Connection Manager where you can open multiple RDP sessions within one snap-in. Here is the brief description of this tool: https://www.microsoft.com/en-us/download/details.aspx?id=44989 A question: In the environment described above, when tests run on dispatchers, sometimes I observe mouse pointer moving on my desktop while Sikuli is being involved on one of the dispatchers. I can't say that it bothers me, but what I am really worried about is whether tests being used simultaneously on some dispatchers can affect each other. May it be possible that mouse clicks or keyboard typing would fail on one of the dispatchers if some mouse clicks or keyboard typing happens on another dispatcher at the same time? Is it possible, or mouse and keyboard using on separate dispatchers I have RDP sessions to are completely independent of each other? Thank you! Cedar -- 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 : sikuli-driver@lists.launchpad.net Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
[Sikuli-driver] [Question #661621]: Using Sikuli in multiple RDP connections
New question #661621 on Sikuli: https://answers.launchpad.net/sikuli/+question/661621 Hi there, First of all, thank you so much for all the work you. Sikuli is the great tool, and it is great you support it and move it forward. With Sikuli, you help lots of people to solve issues they face in automation. My question seems to be a little dummy in some sense, but it is quite important at the same time. It is a dummy because I don't understand in the full extent how Sikuli emulates mouse clicks and keyboard typing, and it is important because we rely on Sikuli heavily. Prehistory: So we are using Sikuli a lot in our automated tests. Here is how it looks like: there are some Windows machines (aka dispatchers) where automated tests run. On each dispatcher, tests start on schedule (by a Windows scheduled tasks), and tests on these dispatchers run simultaneously. For Sikuli to work on each of those dispatchers, you need a Windows user to be logged in. So from my desktop, I have RDP sessions opened to each of those dispatchers. I open these sessions either via mstsc.exe (a standard Windows RDP connection), or with Microsoft Remote Desktop Connection Manager where you can open multiple RDP sessions within one snap-in. Here is the brief description of this tool: https://www.microsoft.com/en-us/download/details.aspx?id=44989 A question: In the environment described above, when tests run on dispatchers, sometimes I observe mouse pointer moving on my desktop while Sikuli is being involved on one of the dispatchers. I can't say that it bothers me, but what I am really worried about is whether tests being used simultaneously on some dispatchers can affect each other. May it be possible that mouse clicks or keyboard typing would fail on one of the dispatchers if some mouse clicks or keyboard typing happens on another dispatcher at the same time? Is it possible, or mouse and keyboard using on separate dispatchers I have RDP sessions to are completely independent of each other? Thank you! Cedar -- 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 : sikuli-driver@lists.launchpad.net Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
[Sikuli-driver] [Bug 1409098] Re: findAll limited to 100 matches
@skeets Agreed: an image that has at least some non-blank parts should be found correctly. What about .exact()? -- You received this bug notification because you are a member of Sikuli Drivers, which is subscribed to Sikuli. https://bugs.launchpad.net/bugs/1409098 Title: findAll limited to 100 matches Status in Sikuli: In Progress Bug description: Calls to findAll seem to report at most 100 matches., silently discarding any further matches. Suggest findAll be configurable to specify the maximum number of matches, even if the default is 100, in the same way that similarity defaults to 0.7 but can be configured. Also suggest that if the max is exceeded, an exception is thrown so that missing matches can be spotted easily To manage notifications about this bug go to: https://bugs.launchpad.net/sikuli/+bug/1409098/+subscriptions ___ 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
[Sikuli-driver] [Bug 1409098] Re: findAll limited to 100 matches
Not sure we can use .exact() correct? Based on my info above? We need to be able to find the blank image at a specific location and if we only find one image at a location (of possibly many locations) then it may not be the image at the location we are looking for. Make sense? -- You received this bug notification because you are a member of Sikuli Drivers, which is subscribed to Sikuli. https://bugs.launchpad.net/bugs/1409098 Title: findAll limited to 100 matches Status in Sikuli: In Progress Bug description: Calls to findAll seem to report at most 100 matches., silently discarding any further matches. Suggest findAll be configurable to specify the maximum number of matches, even if the default is 100, in the same way that similarity defaults to 0.7 but can be configured. Also suggest that if the max is exceeded, an exception is thrown so that missing matches can be spotted easily To manage notifications about this bug go to: https://bugs.launchpad.net/sikuli/+bug/1409098/+subscriptions ___ 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
[Sikuli-driver] [Bug 1409098] Re: findAll limited to 100 matches
@skeets no problem. I will try it myself, since I am interested to fully understand the effect and look, wether it could be corrected somehow. I will let you know about my results. -- You received this bug notification because you are a member of Sikuli Drivers, which is subscribed to Sikuli. https://bugs.launchpad.net/bugs/1409098 Title: findAll limited to 100 matches Status in Sikuli: In Progress Bug description: Calls to findAll seem to report at most 100 matches., silently discarding any further matches. Suggest findAll be configurable to specify the maximum number of matches, even if the default is 100, in the same way that similarity defaults to 0.7 but can be configured. Also suggest that if the max is exceeded, an exception is thrown so that missing matches can be spotted easily To manage notifications about this bug go to: https://bugs.launchpad.net/sikuli/+bug/1409098/+subscriptions ___ 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
[Sikuli-driver] [Bug 1409098] Re: findAll limited to 100 matches
Awesome thanks for the help! FYI, the workaround is working, a blank child image with some "extra stuff" is found every time and where we expect it to be within the parent image using the findall method. -- You received this bug notification because you are a member of Sikuli Drivers, which is subscribed to Sikuli. https://bugs.launchpad.net/bugs/1409098 Title: findAll limited to 100 matches Status in Sikuli: In Progress Bug description: Calls to findAll seem to report at most 100 matches., silently discarding any further matches. Suggest findAll be configurable to specify the maximum number of matches, even if the default is 100, in the same way that similarity defaults to 0.7 but can be configured. Also suggest that if the max is exceeded, an exception is thrown so that missing matches can be spotted easily To manage notifications about this bug go to: https://bugs.launchpad.net/sikuli/+bug/1409098/+subscriptions ___ 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
[Sikuli-driver] [Bug 1409098] Re: findAll limited to 100 matches
@skeets Some first tests with findAll() tell me: - exact() does not change the behavior - a blank image is not found in all possible/expected locations and subsequent matches overlap I will have a deeper look into the implementation, but I doubt, that I can really change something (most of it is still baken in C++ deep down in the inherited hell from the time I took over ;-) ... and I will check what my preflight version 2 is doing here. Thanks for finding, reporting and feedback. BTW: what version of SikuliX do you use? -- You received this bug notification because you are a member of Sikuli Drivers, which is subscribed to Sikuli. https://bugs.launchpad.net/bugs/1409098 Title: findAll limited to 100 matches Status in Sikuli: In Progress Bug description: Calls to findAll seem to report at most 100 matches., silently discarding any further matches. Suggest findAll be configurable to specify the maximum number of matches, even if the default is 100, in the same way that similarity defaults to 0.7 but can be configured. Also suggest that if the max is exceeded, an exception is thrown so that missing matches can be spotted easily To manage notifications about this bug go to: https://bugs.launchpad.net/sikuli/+bug/1409098/+subscriptions ___ 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
[Sikuli-driver] [Bug 1409098] Re: findAll limited to 100 matches
OK cool glad it's not just me. :P Umm we are using 1.1.1. Sikuli Version: SikuliX 1.1.1 OS Version: win 6.1 Java Version: 8 Python Version: 2.7.0 -- You received this bug notification because you are a member of Sikuli Drivers, which is subscribed to Sikuli. https://bugs.launchpad.net/bugs/1409098 Title: findAll limited to 100 matches Status in Sikuli: In Progress Bug description: Calls to findAll seem to report at most 100 matches., silently discarding any further matches. Suggest findAll be configurable to specify the maximum number of matches, even if the default is 100, in the same way that similarity defaults to 0.7 but can be configured. Also suggest that if the max is exceeded, an exception is thrown so that missing matches can be spotted easily To manage notifications about this bug go to: https://bugs.launchpad.net/sikuli/+bug/1409098/+subscriptions ___ 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
[Sikuli-driver] [Bug 1409098] Re: findAll limited to 100 matches
@skeets thanks. fine. Now I am sure, that I see what you see ;-) I will keep you informed. -- You received this bug notification because you are a member of Sikuli Drivers, which is subscribed to Sikuli. https://bugs.launchpad.net/bugs/1409098 Title: findAll limited to 100 matches Status in Sikuli: In Progress Bug description: Calls to findAll seem to report at most 100 matches., silently discarding any further matches. Suggest findAll be configurable to specify the maximum number of matches, even if the default is 100, in the same way that similarity defaults to 0.7 but can be configured. Also suggest that if the max is exceeded, an exception is thrown so that missing matches can be spotted easily To manage notifications about this bug go to: https://bugs.launchpad.net/sikuli/+bug/1409098/+subscriptions ___ 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
Re: [Sikuli-driver] [Question #661621]: Using Sikuli in multiple RDP connections
Question #661621 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/661621 Status: Open => Answered RaiMan proposed the following answer: A SikuliX test case on one physical machine cannot be influenced by any other SikuliX stuff on any other machine - SikuliX itself does not have any feature to do that. If you see any mouse movement on your master machine, then this is caused by the RDP stuff, depending on what you have setup on mouse and keyboard handling. While a test runs in one of your dispatchers, you should see the screen changes in your respective RDP window. Wether you can see the mouse move, again depends on setup and speed aspects. What you never should do, while a test runs on a dispatcher: do not do anything intentionally with mouse and keyboard on the master, while they are catched by the RDP window: this actions would go to the dispatcher and might interfere the test. -- 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 : sikuli-driver@lists.launchpad.net Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
Re: [Sikuli-driver] [Question #661621]: Using Sikuli in multiple RDP connections
Question #661621 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/661621 Status: Answered => Open Cedar is still having a problem: Thank you RaiMan! Do I understand right that a SikuliX test case on one machine cannot be influenced by any other SikuliX stuff on another machine even if these machines are virtual ones running on remote VMware ESXi server, not physical ones? As to mouse and keyboard on the master (physical desktop), I got it, no intentional actions with mouse and keyboard. At the same time, what about common activity? May I just type something in the editor, use mouse in the browser etc? Any chances that such actions would somehow affect SikuliX behavior on dispatchers? Thanks, Cforest -- 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 : sikuli-driver@lists.launchpad.net Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
Re: [Sikuli-driver] [Question #661621]: Using Sikuli in multiple RDP connections
Question #661621 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/661621 Status: Open => Answered RaiMan proposed the following answer: at: Do I understand right that a SikuliX test case... virtual or physical does not matter: the SikuliX features intended to act on mouse and keyboard of the machine, the script/test is running on, do not have any side effects towards other machines. So if the virtual machines itself do not do anything in this direction nor the script itself does it, the tests running on the dispatchers are completely independent from each other. at: As to mouse and keyboard on the master (physical desktop)... Yes, only mouse/keyboard actions inside a dispatcher RDP window might interfere a running test on the dispatcher. For all activities outside an RDP window on the master it is valid, that the master is only another machine like the dispatchers are: independent. Happy testing -- 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 : sikuli-driver@lists.launchpad.net Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
Re: [Sikuli-driver] [Question #661621]: Using Sikuli in multiple RDP connections
Question #661621 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/661621 Status: Answered => Solved Cedar confirmed that the question is solved: Thank you RaiMan! -- 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 : sikuli-driver@lists.launchpad.net Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
[Sikuli-driver] [Bug 1409098] Re: findAll limited to 100 matches
@skeets Ok, with version 1.1.1+ I have to leave you with the workaround for now. Did not find any possibility to change the behavior. It is on the list for version 2. -- You received this bug notification because you are a member of Sikuli Drivers, which is subscribed to Sikuli. https://bugs.launchpad.net/bugs/1409098 Title: findAll limited to 100 matches Status in Sikuli: In Progress Bug description: Calls to findAll seem to report at most 100 matches., silently discarding any further matches. Suggest findAll be configurable to specify the maximum number of matches, even if the default is 100, in the same way that similarity defaults to 0.7 but can be configured. Also suggest that if the max is exceeded, an exception is thrown so that missing matches can be spotted easily To manage notifications about this bug go to: https://bugs.launchpad.net/sikuli/+bug/1409098/+subscriptions ___ 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
[Sikuli-driver] [Question #661634]: Windows IDE-related errors
New question #661634 on Sikuli: https://answers.launchpad.net/sikuli/+question/661634 Hi, I'm installed 1.1.1 and it appeared to install to completion. But double-clicking sikulix.jar in Windows appears to have a Java process running but nothing appears on screen. At least once it said it was running. Running java.exe -jar sikulix.jar I get: "WARNING: Could not open/create prefs root node Software\JavaSoft\Prefs at root 0x8000x. Windows RegCreateKeyEx(...) returned error code 5. ... [error] WindowsHotkey Manager: JIntellitype problem: Could not load JIntellitype.dll from local file system or from inside JAR" I get similar problems from prior version. Any thoughts on how I can get past this error? -- 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 : sikuli-driver@lists.launchpad.net Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
[Sikuli-driver] [Question #661673]: Sikuli- IDE image save to desktop
New question #661673 on Sikuli: https://answers.launchpad.net/sikuli/+question/661673 I am Taking image through SIkuli-IDE and trying to save that image in my Desktop as .png File not as sikuli file for me it is not Working but previously i tried and saved. Help me out i am Using 1.1.2 build sikuli Jars and IDE. How to save that Takenscreenshots to my Deskop as .png File. Thank you. -- 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 : sikuli-driver@lists.launchpad.net Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
Re: [Sikuli-driver] [Question #661634]: Windows IDE-related errors
Question #661634 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/661634 Status: Open => Answered RaiMan proposed the following answer: purge everything from prior Sikuli(X) installations and remove all Sikuli(X) related pointers to anything from prior versions from your system environment. Best if you then start again from scratch. the WARNING can be ignored. -- 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 : sikuli-driver@lists.launchpad.net Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
