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

2 files changed, 2 insertions, 8 deletions

diff --git a/src/tests/testDemandAttention.cc b/src/tests/testDemandAttention.cc
index 10fadb3..914f369 100644
--- a/src/tests/testDemandAttention.cc
+++ b/src/tests/testDemandAttention.cc
@@ -61,10 +61,7 @@ public:
         FbTk::RefCount<FbTk::Command<void> > cmd(new FbTk::SimpleCommand<App>
                                                  (*this,
                                                   &App::demandAttention));
-        timeval t;
-        t.tv_sec = 5;
-        t.tv_usec = 0;
-        m_timer.setTimeout(t);
+        m_timer.setTimeout(5 * FbTk::FbTime::IN_SECONDS);
         m_timer.setCommand(cmd);
         m_timer.fireOnce(false);
         m_timer.start();
diff --git a/src/tests/titletest.cc b/src/tests/titletest.cc
index 9ea94f1..e16435a 100644
--- a/src/tests/titletest.cc
+++ b/src/tests/titletest.cc
@@ -52,10 +52,7 @@ public:
         FbTk::RefCount<FbTk::Command> cmd(new FbTk::SimpleCommand<App>
                                           (*this,
                                            &App::updateTitle));
-        timeval t;
-        t.tv_sec = 0;
-        t.tv_usec = 150000;
-        m_timer.setTimeout(t);
+        m_timer.setTimeout(150 * FbTk::FbTime::IN_MILLISECONDS);
         m_timer.setCommand(cmd);
         m_timer.fireOnce(false);
         m_timer.start();