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.

1 files changed, 3 insertions, 3 deletions

diff --git a/src/FbTk/Timer.cc b/src/FbTk/Timer.cc
index 2404773..1bec893 100644
--- a/src/FbTk/Timer.cc
+++ b/src/FbTk/Timer.cc
@@ -117,7 +117,7 @@ void Timer::start() {
         // it from s_timerlist before restarting it
         stop();
 
-        m_start = FbTk::FbTime::now();
+        m_start = FbTk::FbTime::mono();
 
         // interval timers have their timeout change every 
         // time they are started!
@@ -158,7 +158,7 @@ void Timer::updateTimers(int fd) {
     FD_SET(fd, &rfds);
 
     bool overdue = false;
-    uint64_t now = FbTime::now();
+    uint64_t now = FbTime::mono();
     uint64_t end_time;
 
     // search for overdue timers
@@ -192,7 +192,7 @@ void Timer::updateTimers(int fd) {
 
     static std::vector<FbTk::Timer*> timeouts;
 
-    now = FbTime::now();
+    now = FbTime::mono();
     for (it = s_timerlist.begin(); it != s_timerlist.end(); ++it ) {
         if (now < (*it)->getEndTime()) {
             break;