summaryrefslogtreecommitdiff
path: root/gdk
diff options
context:
space:
mode:
authorGeorges Basile Stavracas Neto <georges.stavracas@gmail.com>2017-10-04 15:33:15 -0300
committerTimm Bäder <mail@baedert.org>2018-01-20 13:10:42 +0100
commit42ff22f222566448b97d4c980b91ac5f66ea9448 (patch)
tree5776691851fd2acaa02bf7f376ef77ce61e98a03 /gdk
parent4d36a0bf352cc69e85a065e49119a7f6804bc9e2 (diff)
downloadgtk+-42ff22f222566448b97d4c980b91ac5f66ea9448.tar.gz
display-x11: Unset tiled state if _GTK_EDGE_CONSTRAINTS is supported
Commit c415bef5de introduced support for the new _GTK_EDGE_CONSTRAINTS atom. If the compositor supports that atom, however, we were always setting the tiled state, even if no actual tiling information is available, where the correct action is to completely remove any traces of the tiled state. Fix that by correctly removing the tiled state when compositor supports _GTK_EDGE_CONSTRAINTS Xatom. https://bugzilla.gnome.org/show_bug.cgi?id=788516
Diffstat (limited to 'gdk')
-rw-r--r--gdk/x11/gdkdisplay-x11.c6
1 files changed, 2 insertions, 4 deletions
diff --git a/gdk/x11/gdkdisplay-x11.c b/gdk/x11/gdkdisplay-x11.c
index fedfada7c1..84a1b2f1ae 100644
--- a/gdk/x11/gdkdisplay-x11.c
+++ b/gdk/x11/gdkdisplay-x11.c
@@ -236,10 +236,8 @@ do_edge_constraint_state_check (GdkWindow *window,
}
else
{
- if (!(old_state & GDK_WINDOW_STATE_TILED))
- {
- local_set |= GDK_WINDOW_STATE_TILED;
- }
+ if (old_state & GDK_WINDOW_STATE_TILED)
+ local_unset |= GDK_WINDOW_STATE_TILED;
}
/* Top edge */