Age | Commit message (Collapse) | Author | Files | Lines | |
---|---|---|---|---|---|
2013-01-26 | Calculates timeouts of ClockTool based upon System Clock | Mathias Gumz | 1 | -10/+14 | |
Users expect time switches to happen upon system clock times. Calculating the timeout for the next refresh of the shown time via the monotonic clock is wrong: The monotonic clock yields values based upon some arbitrary point in time which might be off a little bit to the system clock, a 'full' minute of the monotonic clock might be in the midst of a system clock minute. | |||||
2013-01-02 | Compile fix: forgotten parentheses around value | Mathias Gumz | 1 | -1/+1 | |
2012-08-28 | changed timing functions to use a monotonic increasing clock | Mathias Gumz | 1 | -0/+97 | |
gettimeofday() is subject to be changed on daylight-saving or to ntp-related (think leap-seconds). even worse, it is subject to be changed BACK in time. this is hard to fix correctly (see commit 45726d3016e and bug #3560509). it is irrelevant for timers to know the nano-seconds since the epoch anyways. |