From cacba79d49027ed4f75df311e588292dfae55854 Mon Sep 17 00:00:00 2001 From: Corey Thompson Date: Thu, 8 Dec 2011 21:45:59 -0500 Subject: [PATCH] Initialize floating_geometry on property::border_width signal (FS#826) Initializing the client property "floating_geometry" on the property::geometry signal is problematic since this is emitted before client_set_border_width(), causing the internal client geometry to get stored and later passed to client:geometry() which assumes it includes titlebar and borders. Signed-off-by: Corey Thompson Signed-off-by: Uli Schlachter --- lib/awful/client.lua.in | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/lib/awful/client.lua.in b/lib/awful/client.lua.in index 5846ed6cd..b63a64656 100644 --- a/lib/awful/client.lua.in +++ b/lib/awful/client.lua.in @@ -580,9 +580,9 @@ end capi.client.add_signal("new", function(c) local function store_init_geometry(c) property.set(c, "floating_geometry", c:geometry()) - c:remove_signal("property::geometry", store_init_geometry) + c:remove_signal("property::border_width", store_init_geometry) end - c:add_signal("property::geometry", store_init_geometry) + c:add_signal("property::border_width", store_init_geometry) end) capi.client.add_signal("manage", function(c)