Memory-managed wrapper type.

Type class for types which can be safely cast to FrameClock, for instance with toFrameClock.

Cast to FrameClock, for types for which this is known to be safe. For general casts, use castTo.

A convenience alias for Nothing :: Maybe FrameClock.

Starts updates for an animation. Until a matching call to frameClockEndUpdating is made, the frame clock will continually request a new frame with the FrameClockPhaseUpdate phase. This function may be called multiple times and frames will be requested until frameClockEndUpdating is called the same number of times.

Since: 3.8

Stops updates for an animation. See the documentation for frameClockBeginUpdating.

Since: 3.8

Gets the frame timings for the current frame.

Since: 3.8

A FrameClock maintains a 64-bit counter that increments for each frame drawn.

Since: 3.8

Gets the time that should currently be used for animations. Inside the processing of a frame, it’s the time used to compute the animation position of everything in a frame. Outside of a frame, it's the time of the conceptual “previous frame,” which may be either the actual previous frame time, or if that’s too old, an updated time.

Since: 3.8

FrameClock internally keeps a history of FrameTimings objects for recent frames that can be retrieved with frameClockGetTimings. The set of stored frames is the set from the counter values given by frameClockGetHistoryStart and frameClockGetFrameCounter, inclusive.

Since: 3.8

Using the frame history stored in the frame clock, finds the last known presentation time and refresh interval, and assuming that presentation times are separated by the refresh interval, predicts a presentation time that is a multiple of the refresh interval after the last presentation time, and later than baseTime.

Since: 3.8

Retrieves a FrameTimings object holding timing information for the current frame or a recent frame. The FrameTimings object may not yet be complete: see frameTimingsGetComplete.

Since: 3.8

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 frameClockRequestPhase will be combined together and only one frame processed. If you are displaying animated content and want to continually request the FrameClockPhaseUpdate phase for a period of time, you should use frameClockBeginUpdating instead, since this allows GTK+ to adjust system parameters to get maximally smooth animations.

Since: 3.8

Type for the callback on the (unwrapped) C side.

This signal ends processing of the frame. Applications should generally not handle this signal.

Connect a signal handler for the “after-paint” signal, to be run after the default handler. When overloading is enabled, this is equivalent to

after frameClock #afterPaint callback

Wrap the callback into a Closure.

Generate a function pointer callable from C code, from a C_FrameClockAfterPaintCallback.

A convenience synonym for Nothing :: Maybe FrameClockAfterPaintCallback.

Connect a signal handler for the “after-paint” signal, to be run before the default handler. When overloading is enabled, this is equivalent to

on frameClock #afterPaint callback

Wrap a FrameClockAfterPaintCallback into a C_FrameClockAfterPaintCallback.

Type for the callback on the (unwrapped) C side.

This signal begins processing of the frame. Applications should generally not handle this signal.

Connect a signal handler for the “before-paint” signal, to be run after the default handler. When overloading is enabled, this is equivalent to

after frameClock #beforePaint callback

Wrap the callback into a Closure.

Generate a function pointer callable from C code, from a C_FrameClockBeforePaintCallback.

A convenience synonym for Nothing :: Maybe FrameClockBeforePaintCallback.

Connect a signal handler for the “before-paint” signal, to be run before the default handler. When overloading is enabled, this is equivalent to

on frameClock #beforePaint callback

Wrap a FrameClockBeforePaintCallback into a C_FrameClockBeforePaintCallback.

Type for the callback on the (unwrapped) C side.

This signal is used to flush pending motion events that are being batched up and compressed together. Applications should not handle this signal.

Connect a signal handler for the “flush-events” signal, to be run after the default handler. When overloading is enabled, this is equivalent to

after frameClock #flushEvents callback

Wrap the callback into a Closure.

Generate a function pointer callable from C code, from a C_FrameClockFlushEventsCallback.

A convenience synonym for Nothing :: Maybe FrameClockFlushEventsCallback.

Connect a signal handler for the “flush-events” signal, to be run before the default handler. When overloading is enabled, this is equivalent to

on frameClock #flushEvents callback

Wrap a FrameClockFlushEventsCallback into a C_FrameClockFlushEventsCallback.

Type for the callback on the (unwrapped) C side.

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.

Connect a signal handler for the “layout” signal, to be run after the default handler. When overloading is enabled, this is equivalent to

after frameClock #layout callback

Wrap the callback into a Closure.

Generate a function pointer callable from C code, from a C_FrameClockLayoutCallback.

A convenience synonym for Nothing :: Maybe FrameClockLayoutCallback.

Connect a signal handler for the “layout” signal, to be run before the default handler. When overloading is enabled, this is equivalent to

on frameClock #layout callback

Wrap a FrameClockLayoutCallback into a C_FrameClockLayoutCallback.

Type for the callback on the (unwrapped) C side.

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 produces expose events, which are turned into GTK+ GtkWidget::draw signals.

Connect a signal handler for the “paint” signal, to be run after the default handler. When overloading is enabled, this is equivalent to

after frameClock #paint callback

Wrap the callback into a Closure.

Generate a function pointer callable from C code, from a C_FrameClockPaintCallback.

A convenience synonym for Nothing :: Maybe FrameClockPaintCallback.

Connect a signal handler for the “paint” signal, to be run before the default handler. When overloading is enabled, this is equivalent to

on frameClock #paint callback

Wrap a FrameClockPaintCallback into a C_FrameClockPaintCallback.

Type for the callback on the (unwrapped) C side.

This signal is emitted after processing of the frame is finished, and is handled internally by GTK+ to resume normal event processing. Applications should not handle this signal.

Connect a signal handler for the “resume-events” signal, to be run after the default handler. When overloading is enabled, this is equivalent to

after frameClock #resumeEvents callback

Wrap the callback into a Closure.

Generate a function pointer callable from C code, from a C_FrameClockResumeEventsCallback.

A convenience synonym for Nothing :: Maybe FrameClockResumeEventsCallback.

Connect a signal handler for the “resume-events” signal, to be run before the default handler. When overloading is enabled, this is equivalent to

on frameClock #resumeEvents callback

Wrap a FrameClockResumeEventsCallback into a C_FrameClockResumeEventsCallback.

Type for the callback on the (unwrapped) C side.

This signal is emitted as the first step of toolkit and application processing of the frame. Animations should be updated using frameClockGetFrameTime. Applications can connect directly to this signal, or use gtk_widget_add_tick_callback() as a more convenient interface.

Connect a signal handler for the “update” signal, to be run after the default handler. When overloading is enabled, this is equivalent to

after frameClock #update callback

Wrap the callback into a Closure.

Generate a function pointer callable from C code, from a C_FrameClockUpdateCallback.

A convenience synonym for Nothing :: Maybe FrameClockUpdateCallback.

Connect a signal handler for the “update” signal, to be run before the default handler. When overloading is enabled, this is equivalent to

on frameClock #update callback

Wrap a FrameClockUpdateCallback into a C_FrameClockUpdateCallback.