4f8643cea3
While each stage has at most a GdkFrameClock, the same GdkFrameClock instance may drive multiple stages per frame. This means that the mapping between a GdkFrameClock and a ClutterStage is a 1:M one, not a 1:1. We should store a list of stages associated to each frame clock instance, so that we can iterate over it when we need to update the stages. This commit fixes redraws of applications using multiple stages, especially when using clutter-gtk. |
||
---|---|---|
.. | ||
clutter-backend-gdk-private.h | ||
clutter-backend-gdk.c | ||
clutter-backend-gdk.h | ||
clutter-device-manager-gdk.c | ||
clutter-device-manager-gdk.h | ||
clutter-event-gdk.c | ||
clutter-gdk.h | ||
clutter-input-device-gdk.c | ||
clutter-input-device-gdk.h | ||
clutter-master-clock-gdk.c | ||
clutter-master-clock-gdk.h | ||
clutter-settings-gdk.h | ||
clutter-stage-gdk.c | ||
clutter-stage-gdk.h |