Blame SOURCES/0001-workspacesView-Work-around-spurious-allocation-chang.patch

35159f
From b69b404118852f7955f60d1814f5e19ad61ce449 Mon Sep 17 00:00:00 2001
35159f
From: =?UTF-8?q?Florian=20M=C3=BCllner?= <fmuellner@gnome.org>
35159f
Date: Fri, 12 Jul 2019 03:26:51 +0000
35159f
Subject: [PATCH] workspacesView: Work around spurious allocation changes
35159f
35159f
For some reason, people are still seeing those after commit d5ebd8c8.
35159f
While this is something we really should figure out, we can work around
35159f
the issue by keeping the view actors hidden until the update is complete.
35159f
35159f
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1065
35159f
---
35159f
 js/ui/workspacesView.js | 5 +++++
35159f
 1 file changed, 5 insertions(+)
35159f
35159f
diff --git a/js/ui/workspacesView.js b/js/ui/workspacesView.js
35159f
index 069937d5a..e302296a6 100644
35159f
--- a/js/ui/workspacesView.js
35159f
+++ b/js/ui/workspacesView.js
35159f
@@ -666,10 +666,15 @@ var WorkspacesDisplay = class {
35159f
                                                this._scrollValueChanged.bind(this));
35159f
             }
35159f
 
35159f
+            // HACK: Avoid spurious allocation changes while updating views
35159f
+            view.actor.hide();
35159f
+
35159f
             this._workspacesViews.push(view);
35159f
             Main.layoutManager.overviewGroup.add_actor(view.actor);
35159f
         }
35159f
 
35159f
+        this._workspacesViews.forEach(v => v.actor.show());
35159f
+
35159f
         this._updateWorkspacesFullGeometry();
35159f
         this._updateWorkspacesActualGeometry();
35159f
     }
35159f
-- 
35159f
2.21.0
35159f