diff options
author | Yariv Barkan <21448-yarivb@users.noreply.gitlab.gnome.org> | 2020-05-31 00:23:24 +0300 |
---|---|---|
committer | Alexander Larsson <alexl@redhat.com> | 2020-06-05 11:57:49 +0200 |
commit | f5de46670b4c6bca15a015302e858b72f43498a9 (patch) | |
tree | f51c913b7a88c976a976d89edacfc976d214a49e /gdk/gdkframeclockidle.c | |
parent | 91af8a705b74db6ede1a4e5f0793f44e91b1ffa4 (diff) | |
download | gtk+-f5de46670b4c6bca15a015302e858b72f43498a9.tar.gz |
frame clock: schedule in refresh intervals
When the application does not receive "frame drawn" signals we schedule
the clock to run more or less at intervals equal to the last known
refresh interval. In order to minimize clock skew we have to aim for
exact intervals.
Diffstat (limited to 'gdk/gdkframeclockidle.c')
-rw-r--r-- | gdk/gdkframeclockidle.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/gdk/gdkframeclockidle.c b/gdk/gdkframeclockidle.c index 3b54429bf6..1a345c8ec0 100644 --- a/gdk/gdkframeclockidle.c +++ b/gdk/gdkframeclockidle.c @@ -559,7 +559,7 @@ gdk_frame_clock_paint_idle (void *data) if (priv->freeze_count == 0) { priv->min_next_frame_time = compute_min_next_frame_time (clock_idle, - priv->frame_time); + priv->smoothed_frame_time_base); maybe_start_idle (clock_idle, FALSE); } |