From ffdc032e7017c9d8113dc3a0f096089aca229430 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ole=20J=C3=B8rgen=20Br=C3=B8nner?= Date: Tue, 10 Oct 2017 20:40:46 +0200 Subject: [PATCH] Don't relayout the minimap on "allocation-change" This signal is triggered way too often and there is no realistic scenarios where its needed atm. (window's doesn't change size at will) --- minimap.js | 13 ------------- 1 file changed, 13 deletions(-) diff --git a/minimap.js b/minimap.js index bde18e4..299ed5d 100644 --- a/minimap.js +++ b/minimap.js @@ -13,12 +13,6 @@ calcOffset = function(metaWindow) { return [x_offset, y_offset]; } -allocationChanged = function allocationChanged(actor, propertySpec) { - this.layout(this.clones); -} - -notifySignal = Symbol(); - WindowCloneLayout = new Lang.Class({ Name: 'PaperWindowCloneLayout', Extends: Clutter.LayoutManager, @@ -98,15 +92,8 @@ const Minimap = new Lang.Class({ name: "window-clone-container" }); clone.meta_window = mw; - if (windowActor[notifySignal]) { - windowActor.disconnect(windowActor[notifySignal]); - } - windowActor[notifySignal] = windowActor.connect("notify::allocation", - Lang.bind(this, dynamic_function_ref("allocationChanged"))); container.add_actor(clone); - // let [x_offset, y_offset] = calcOffset(clone.meta_window); - // clone.set_position(-x_offset, -y_offset); return container; });