Go to file
Owen W. Taylor f163a15b13 MetaStackTracker: optimize out unnecessary X restacking
We have a quite accurate view of the X stack, so there's no good reason to ask
the X server to do restacking that has no effect. (Restackings that have no
effect on either X windows or Wayland windows were generally optimized out in
the synchronization code, but in other cases like moving an X window that is
only beneath Wayland windows to the top of the stack we would make such
requests.)

Removing such requests:
 - Is a small efficiency win in itself
 - Allows us to immediately go ahead and apply Wayland changes to the verified stack
 - Prevents queued Wayland changes piling up waiting for an X event that will never
   be received, since the X server will not send confirmation of no-op restacks.

Since such operations may still have an effect on the relative stacking of X
and Wayland windows, we need to continue applying them to the local stack.

https://bugzilla.gnome.org/show_bug.cgi?id=736559
2014-09-12 13:42:56 -04:00
data Add hidden -backward bindings to 50-mutter-navigation.xml 2014-08-17 19:29:43 +02:00
doc
po
src MetaStackTracker: optimize out unnecessary X restacking 2014-09-12 13:42:56 -04:00
tools
.gitignore Add missing file from test framework 2014-09-12 13:40:33 -04:00
autogen.sh
configure.ac Add a test framework and stacking tests 2014-09-12 13:14:51 -04:00
COPYING Updated obsolete FSF postal address in COPYING 2014-01-12 08:44:30 +07:00
Makefile.am
mutter.doap
NEWS Bump version to 3.13.91 2014-09-03 14:03:45 +02:00