fluxbox

Author SHA1 Message Date

Author	SHA1	Message	Date
Mathias Gumz	716532dd47	Calculates timeouts of ClockTool based upon System Clock 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-26 09:21:47 +01:00
Mathias Gumz	541c8c407b	changed timing functions to use a monotonic increasing clock 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 `45726d3016` and bug #3560509). it is irrelevant for timers to know the nano-seconds since the epoch anyways.	2012-08-28 10:51:55 +02:00

Mathias Gumz

716532dd47

Calculates timeouts of ClockTool based upon System Clock

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-26 09:21:47 +01:00

Mathias Gumz

541c8c407b

changed timing functions to use a monotonic increasing clock

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 45726d3016 and bug #3560509). it is
irrelevant for timers to know the nano-seconds since the epoch anyways.

2012-08-28 10:51:55 +02:00

2 commits