sikuli-driver team mailing list archive
-
sikuli-driver team
-
Mailing list archive
-
Message #00342
[Bug 672581] Re: [request] non-continuous wait needed
** Changed in: sikuli
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.
https://bugs.launchpad.net/bugs/672581
Title:
[request] non-continuous wait needed
Status in Sikuli:
Fix Released
Bug description:
I found that using "wait" seems to be chewing a lot of CPU cycles and impacts the underlying app I am trying to test.
When I run Sikuli and the test application on separate machines there are no problems. However when I run the sikuli and the test app on the same machine, sikuli slows down the test app significantly.
I narrowed the problem down to the "wait" statement. I timed the test
app when I did wait(non-existent-image,100) and I saw that the
underlying app response was x5 times slower at the least.
Of course I can write my own "mywait" that will do something like:
attempts=NN
while not exists(img) and attempts>0:
sleep(2)
attempts=attempts-1
Ideally I would like to be able to tell "wait" to examine screen at
certain interval, not continuously.
see question 132797