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
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 form hh: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:
introduce an optional bool-flag in tzdata and correct the time accordingly by the global interval value.
introduce an optional correction value to tzdata by which the clocktime can be adjusted.
Would either of these options be merged upstream?
The text was updated successfully, but these errors were encountered:
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:
interval
value.Would either of these options be merged upstream?
The text was updated successfully, but these errors were encountered: