[Windows] One TimeTicks clock: efficient/reliable high-res, with low-res fallback.

ui/gfx/frame_time.h

Index: ui/gfx/frame_time.h
diff --git a/ui/gfx/frame_time.h b/ui/gfx/frame_time.h
index dd00fbfdd5ddfa908cdacc35ae9535a4070e1617..58b27cb05773b9a4ff1c9943eef14920661b6b56 100644
--- a/ui/gfx/frame_time.h
+++ b/ui/gfx/frame_time.h
@@ -15,8 +15,6 @@ namespace gfx {
 class FrameTime {
  public:
   static base::TimeTicks Now() {
-    if (TimestampsAreHighRes())
-      return base::TimeTicks::HighResNow();
     return base::TimeTicks::Now();
   }
 
@@ -29,8 +27,10 @@ class FrameTime {
 
   static bool TimestampsAreHighRes() {
 #if defined(OS_WIN)
-    return base::TimeTicks::IsHighResClockWorking();
+    return base::TimeTicks::IsHighResolution();

[jamesr, 2015/01/08 20:31:54]

imo you should just delete this, it's not producing anything useful

[brianderson, 2015/01/08 21:10:36]

Opened a bug to remove the whole gfx::FrameTime class:
https://code.google.com/p/chromium/issues/detail?id=447329

[miu, 2015/01/08 22:16:00]

What do you mean by "delete this?"  Are you referring to this method, or the
whole FrameTime class?

Either way, I'd prefer to follow-up with this in a later clean-up change.  (I've
already been maintaining a TODO list to track several other clean-up items
resulting from this change.)

[miu, 2015/01/08 22:16:00]

Acknowledged.

 #else
+    // TODO(miu): Mac/Linux always provide high-resolution timestamps.  Consider
+    // returning base::TimeTicks::IsHighResolution() for all platforms.
     return false;
 #endif
   }