Queues an animation frame update and adds a callback to be called
before each frame. Until the tick callback is removed, it will be
called frequently (usually at the frame rate of the output device
or as quickly as the application can be repainted, whichever is
slower). For this reason, is most suitable for handling graphics
that change every frame or every few frames. The tick callback does
not automatically imply a relayout or repaint. If you want a
repaint or relayout, and aren’t changing widget properties that
would trigger that (for example, changing the text of a gtk.Label),
then you will have to call Widget.queueResize or
Widget.queueDrawArea yourself.
This is a more convenient alternative to connecting directly to the
update signal of gdk.FrameClock, since you don't
have to worry about when a gdk.FrameClock is assigned to a widget.
Queues an animation frame update and adds a callback to be called before each frame. Until the tick callback is removed, it will be called frequently (usually at the frame rate of the output device or as quickly as the application can be repainted, whichever is slower). For this reason, is most suitable for handling graphics that change every frame or every few frames. The tick callback does not automatically imply a relayout or repaint. If you want a repaint or relayout, and aren’t changing widget properties that would trigger that (for example, changing the text of a gtk.Label), then you will have to call Widget.queueResize or Widget.queueDrawArea yourself.
Frame.clockGetFrameTime should generally be used for timing continuous animations and Frame.timingsGetPredictedPresentationTime if you are trying to display isolated frames at particular times.
This is a more convenient alternative to connecting directly to the update signal of gdk.FrameClock, since you don't have to worry about when a gdk.FrameClock is assigned to a widget.