[gnome-shell/wip/carlosg/no-layout-on-chrome-container: 4/4] layout: Mark chrome container as NO_LAYOUT
- From: Florian Müllner <fmuellner src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [gnome-shell/wip/carlosg/no-layout-on-chrome-container: 4/4] layout: Mark chrome container as NO_LAYOUT
- Date: Tue, 14 Aug 2018 17:13:26 +0000 (UTC)
commit 5e83baa5c187ca9474198b6a2511c97753db81c8
Author: Carlos Garnacho <carlosg gnome org>
Date: Fri Aug 10 21:37:48 2018 +0200
layout: Mark chrome container as NO_LAYOUT
Showing and hiding children does not affect the allocation of the uiGroup
nor its other children. We can avoid full relayout/redraw in those
situations.
js/ui/layout.js | 1 +
1 file changed, 1 insertion(+)
---
diff --git a/js/ui/layout.js b/js/ui/layout.js
index 210fb667a..7a3cb227d 100644
--- a/js/ui/layout.js
+++ b/js/ui/layout.js
@@ -204,6 +204,7 @@ var LayoutManager = new Lang.Class({
// Set up stage hierarchy to group all UI actors under one container.
this.uiGroup = new Shell.GenericContainer({ name: 'uiGroup' });
+ this.uiGroup.set_flags(Clutter.ActorFlags.NO_LAYOUT);
this.uiGroup.connect('allocate', (actor, box, flags) => {
let children = actor.get_children();
for (let i = 0; i < children.length; i++)
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]