a625e2b79a
Any timer_module based module would sleep for the set interval and then continue running. Depending on the start time of polybar this sleep pattern might not be aligned, which causes such modules to always update in a shifted manner. Consider the date module as an example. If the update interval is set to 60 seconds and polybar was started at 13:37:37, polybar would update the clock at 13:38:37, 13:39:37 and so on. To make matters worse, if a module would perform lengthy checks this interval might drift over time, causing even more inconsistent updating. This patch extends the base module with a sleep_until method that calls the corresponding function on the sleephandler. Additionally the timer_module is extended to compute the remaining time until the next interval passes and sleep accordingly. Closes #2064 Co-developed-by: Dominik Töllner <dominik.toellner@stud.uni-hannover.de> Co-authored-by: Malte Bargholz <malte@screenri.de> |
||
|---|---|---|
| .. | ||
| base.hpp | ||
| base.inl | ||
| event_handler.hpp | ||
| event_module.hpp | ||
| factory.hpp | ||
| inotify_module.hpp | ||
| input_handler.hpp | ||
| static_module.hpp | ||
| timer_module.hpp | ||