[mutter] clutter/stage-view: Initialize view as damaged and awaiting frame
- From: Marge Bot <marge-bot src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [mutter] clutter/stage-view: Initialize view as damaged and awaiting frame
- Date: Sun, 22 Aug 2021 17:31:28 +0000 (UTC)
commit 18c414cca422ee818b42066f2633e59a4f942ab4
Author: Jonas Ã…dahl <jadahl gmail com>
Date: Fri Jul 30 11:28:28 2021 +0200
clutter/stage-view: Initialize view as damaged and awaiting frame
Make sure that when we've recreated views that we'll actually paint a
new frame for it. This was very rarely a problem, as views tend to
result in getting damage etc being queued as side effects of various
things, like layout, but e.g. when running certain tests, this might not
happen. There is no situation where we want to create a new view that
should remain unpainted, so just make sure we initialize it to become up
to date.
Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1947>
clutter/clutter/clutter-stage-view.c | 3 +++
1 file changed, 3 insertions(+)
---
diff --git a/clutter/clutter/clutter-stage-view.c b/clutter/clutter/clutter-stage-view.c
index 2b2cadd684..9b7345983c 100644
--- a/clutter/clutter/clutter-stage-view.c
+++ b/clutter/clutter/clutter-stage-view.c
@@ -1369,6 +1369,9 @@ clutter_stage_view_constructed (GObject *object)
&frame_clock_listener_iface,
view);
+ clutter_stage_view_add_redraw_clip (view, NULL);
+ clutter_stage_view_schedule_update (view);
+
G_OBJECT_CLASS (clutter_stage_view_parent_class)->constructed (object);
}
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]