WatchMaker Feature Requests All the ideas and discussions
4 votes Vote

Time (current, cal start/stop) in UNIX seconds

Making calendar event start/stop and current time available in UNIX seconds (seconds since 1970) would make dealing with multi-day / long duration events trivial in scripting. Basically it would allow

((cal1_ssec < time_sec) and (cal1_esec > time_sec)) and 'In the event!' or 'not in the event'

No matter when the event started (possibly days ago) and ends (possibly days in the future). This way you wouldn't have to do complex considerations of whether start > end or end > start to determine your % range of the event.

(You don't need to do this in seconds necessarily, days since 1970 or hours or something else fractional could work too, as long as they are from a fixed point in time).

Christopher Ashton , 07.05.2015, 17:38
Idea status: under consideration


Christopher Ashton, 07.05.2015, 17:49
I should add, currently I'm assuming that WatchMaker either doesn't support events longer than 24h at all, or breaks the event up into a series of 24h events. This would add support for the long events.
gregmac, 22.06.2017, 14:30
The current state is far worse than that.

Let's say it's 9am. Event 1 begins at 10am and ends at 11am. You currently can't tell the difference between that event starting at 10am today (1 hour from now), or 10am yesterday (23 hours ago -- which means it's in progress)!
There's several more examples of this type of thing.

I came here looking for an offset from current time for start and end (seconds difference, negative values indicating in the past), but unix seconds would be just as easy.

I am trying to display the next 3 events as arcs around the outside of the watch, with the conditions:

* Only show the next 12 hours
* If an event starts in the past, then display the arc beginning "now" (basically, just show the remainder of the event)
* If an event ends more than 12 hours from now, display the arc ending 12 hours from now (don't wrap around and overlap current time)

I'm finding this is literally impossible to do accurately. It works if events are all short, but starts displaying inaccurately as soon as they start or end more than 12 hours from current time.

Leave a comment