Open cherti opened 4 years ago
I'd like to send a PR for this - is it likely to be a feature that would be accepted?
@cherti could you elaborate on how the two implentations you outlined would work? I'm unable to understand them.
@Flying-Toast tzdata is the variable holding the time info that is displayed, somewhere in i3status (iirc, been a while since I looked).
Currently,
i3status
has a refresh interval and all widgets are updated according to this interval.Assume, for the sake of argument, we use a
tztime
widget in the formhh:mm
, showing hours and minutes of the current time and an interval time of 60s. In this configuration, the clock is behind the actual time for a certain amount of time (varying from 1s to 59s, depending on how i3status' refresh coincides with the actual minute turnover).For some people it is preferrable to have the
tztime
widget advance the clock instead of lagging behind.This could be implemented in two ways: 1) introduce an optional bool-flag in tzdata and correct the time accordingly by the global
interval
value. 2) introduce an optional correction value to tzdata by which the clocktime can be adjusted.Would either of these options be merged upstream?