-
Notifications
You must be signed in to change notification settings - Fork 18
Loop task can be set to a timestamp #28
Comments
@masterofhash do you think this would be possible to be implemented? |
This shouldn't be hard, we'll need to make sure the GUI changes are backwards compatible in terms of JSON serializing / deserializing to ensure it doesn't break people's existing saved configs |
Yeah that's true. Would you want to do a full loop or check the time at each step in the loop and short circuit the loop @realpoke ? |
I think it would be best to have it stop as soon as it hits the timestamp, so to short sircuit the loop would be great if possible :D |
Oh okay, I was thinking the "Stop at end of loop" approach. I'm good with either one, though. We could also have a "Timestamp" input and an "Interrupt Loop" checkbox button? |
I think timestamp and an interrupt option makes the most sense here. |
That’s good with me.
…On Thu, Jan 10, 2019 at 1:12 PM Explv ***@***.***> wrote:
I think timestamp and an interrupt option makes the most sense here.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#28 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AsO3hmke_Xe1b09f74_lMowxx3d95S9Zks5vB565gaJpZM4Z44yV>
.
|
It would be great if the loop task had an option to set a timestamp, so that it would keep looping until that specific time.
Could either be with a specific date or just a time of the day.
The text was updated successfully, but these errors were encountered: