gdk_window_set_debug_updates
gdk_window_enable_synchronized_configure
gdk_window_configure_finished
+gdk_window_get_frame_clock
<SUBSECTION>
gdk_window_set_user_data
gdk_test_simulate_button
gdk_test_simulate_key
</SECTION>
+
+<SECTION>
+<TITLE>GdkFrameClock</TITLE>
+<FILE>gdkframeclock</FILE>
+GdkFrameClock
+gdk_frame_clock_get_frame_time
+GdkFrameClockPhase
+gdk_frame_clock_request_phase
+gdk_frame_clock_begin_updating
+gdk_frame_clock_end_updating
+gdk_frame_clock_get_frame_counter
+gdk_frame_clock_get_history_start
+gdk_frame_clock_get_timings
+gdk_frame_clock_get_current_timings
+gdk_frame_clock_get_refresh_info
+<SUBSECTION Private>
+GdkFrameClockPrivate
+gdk_frame_clock_get_type
+</SECTION>
+
+<SECTION>
+<TITLE>GdkFrameTimings</TITLE>
+<FILE>gdkframetimings</FILE>
+GdkFrameTimings
+gdk_frame_timings_ref
+gdk_frame_timings_unref
+gdk_frame_timings_get_frame_counter
+gdk_frame_timings_get_complete
+gdk_frame_timings_get_frame_time
+gdk_frame_timings_get_presentation_time
+gdk_frame_timings_get_refresh_interval
+gdk_frame_timings_get_predicted_presentation_time
+<SUBSECTION Private>
+gdk_frame_get_type
+</SECTION>
#include "gdkinternals.h"
/**
- * SECTION:frameclock
+ * SECTION:gdkframeclock
* @Short_description: Frame clock syncs painting to a window or display
* @Title: Frame clock
*
* sense for the synchronization being implemented, the clock will
* process a frame and emit signals for each phase that has been
* requested. (See the signals of the #GdkFrameClock class for
- * documentation of the phases. GDK_FRAME_CLOCK_PHASE_UPDATE and the
- * ::update signal are most interesting for application writers, and
- * are used to update the animations, using the frame time given by
- * gdk_frame_clock_get_frame_time().
+ * documentation of the phases. %GDK_FRAME_CLOCK_PHASE_UPDATE and the
+ * #GdkFrameClock::update signal are most interesting for application
+ * writers, and are used to update the animations, using the frame time
+ * given by gdk_frame_clock_get_frame_time().
*
* The frame time is reported in microseconds and generally in the same
* timescale as g_get_monotonic_time(), however, it is not the same
* are called at a "similar" time get the same value. This means that
* if different animations are timed by looking at the difference in
* time between an initial value from gdk_frame_clock_get_frame_time()
- * and the value inside the ::update signal of the clock, they will
- * stay exactly synchronized.
+ * and the value inside the #GdkFrameClock::update signal of the clock,
+ * they will stay exactly synchronized.
*/
G_DEFINE_ABSTRACT_TYPE (GdkFrameClock, gdk_frame_clock, G_TYPE_OBJECT)
* This signal is emitted as the second step of toolkit and
* application processing of the frame. Any work to update
* sizes and positions of application elements should be
- * performed. GTK normally handles this internally.
+ * performed. GTK+ normally handles this internally.
*/
signals[LAYOUT] =
g_signal_new (g_intern_static_string ("layout"),
* This signal is emitted as the third step of toolkit and
* application processing of the frame. The frame is
* repainted. GDK normally handles this internally and
- * produce expose events, which are turned into GTK
- * GtkWidget::draw signals.
+ * produces expose events, which are turned into GTK+
+ * #GtkWidget::draw signals.
*/
signals[PAINT] =
g_signal_new (g_intern_static_string ("paint"),
* Asks the frame clock to run a particular phase. The signal
* corresponding the requested phase will be emitted the next
* time the frame clock processes. Multiple calls to
- * gdk_frame_clock_request_phase() will be combined togethe
+ * gdk_frame_clock_request_phase() will be combined together
* and only one frame processed. If you are displaying animated
* content and want to continually request the
* %GDK_FRAME_CLOCK_PHASE_UPDATE phase for a period of time,