Closed zoton2 closed 4 years ago
Currently just implemented a simple keyed object with the time in it, could add run data if it's needed.
Should find a better way of storing this while working on v2 release before it's fully released.
Tweaked in dev
branch to make the replicant store a whole copy of the timer, keyed by the ID (which are now actually UUIDs).
I thought about putting this in the schedule data, but then a schedule reimport would remove it. Probably it's own replicant would work with an object that has a key of the ID of the run; maybe also store the run data along with it.