You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 14, 2018. It is now read-only.
Hi RaiMan, I was wondering if there was a specific rationale behind why the Observer/OberserverEvent classes' repeat() takes a long instead of a float as a parameter.
It seems reasonable to want to repeat the next iteration of the observer in a fraction of a second and not just full seconds. Also, with the current code, calling repeat with 0 (event.repeat(0)) or no parameters (event.repeat()) defaults the wait to 1 second instead of 0, which I believe is the expect result.
For the record, I've worked around the issue of not being able to set a sub-1-second delay by overriding sikuli's settings: sikuli.Settings.RepeatWaitTime = 0 (default is 1) which actually results in the 0-second delay I was expecting.
I'm not sure what the ongoing support schedule is for 1.1.x but I wanted to bring this up in case it is an unintended behavior.
Thanks!
The text was updated successfully, but these errors were encountered:
Hi RaiMan, I was wondering if there was a specific rationale behind why the
Observer
/OberserverEvent
classes'repeat()
takes along
instead of afloat
as a parameter.The relevant code is in
ObserverEvent
andObserver
.It seems reasonable to want to repeat the next iteration of the observer in a fraction of a second and not just full seconds. Also, with the current code, calling
repeat
with 0 (event.repeat(0)
) or no parameters (event.repeat()
) defaults the wait to 1 second instead of 0, which I believe is the expect result.For the record, I've worked around the issue of not being able to set a sub-1-second delay by overriding sikuli's settings:
sikuli.Settings.RepeatWaitTime = 0
(default is 1) which actually results in the 0-second delay I was expecting.I'm not sure what the ongoing support schedule is for 1.1.x but I wanted to bring this up in case it is an unintended behavior.
Thanks!
The text was updated successfully, but these errors were encountered: