summaryrefslogtreecommitdiff
path: root/gdk/gdkframeclock.h
diff options
context:
space:
mode:
authorOwen W. Taylor <otaylor@fishsoup.net>2013-02-15 17:04:39 -0500
committerAlexander Larsson <alexl@redhat.com>2013-02-18 17:14:24 +0100
commit1db87c897f930171646351c99af7df09dc7ec949 (patch)
tree7b7783b11fa91636cac8c0cc6380dff150b02656 /gdk/gdkframeclock.h
parent1da329b2bd0bcf1303d9cc557055f77482420967 (diff)
downloadgtk+-1db87c897f930171646351c99af7df09dc7ec949.tar.gz
Add gdk_frame_clock_begin/end_updating()
Add an API to start or stop continually updating the frame clock. This is a slight convenience for applcations and avoids the problem of getting one more frame run after an animation stops, but the primary motivation for this is because it looks like we might have to use timeBeginPeriod()/timeEndPeriod() on Windows to get reasonably accurate timing, and for that we'll need to know if there is an animation running. https://bugzilla.gnome.org/show_bug.cgi?id=693934
Diffstat (limited to 'gdk/gdkframeclock.h')
-rw-r--r--gdk/gdkframeclock.h5
1 files changed, 5 insertions, 0 deletions
diff --git a/gdk/gdkframeclock.h b/gdk/gdkframeclock.h
index f6529795af..a82d5cf594 100644
--- a/gdk/gdkframeclock.h
+++ b/gdk/gdkframeclock.h
@@ -82,6 +82,11 @@ GDK_AVAILABLE_IN_3_8
void gdk_frame_clock_request_phase (GdkFrameClock *frame_clock,
GdkFrameClockPhase phase);
+GDK_AVAILABLE_IN_3_8
+void gdk_frame_clock_begin_updating (GdkFrameClock *frame_clock);
+GDK_AVAILABLE_IN_3_8
+void gdk_frame_clock_end_updating (GdkFrameClock *frame_clock);
+
/* Frame history */
GDK_AVAILABLE_IN_3_8
gint64 gdk_frame_clock_get_frame_counter (GdkFrameClock *frame_clock);