1
0
Fork 0
mutter-performance-source/doc/reference
Jasper St. Pierre aec3edb1cc Always map the client and frame windows
Traditionally, WMs unmap windows when minimizing them, and map them
when restoring them or wanting to show them for other reasons, like
upon creation.

However, as metacity morphed into mutter, we optionally chose to keep
windows mapped for the lifetime of the window under the user option
"live-window-previews", which makes the code keep windows mapped so it
can show window preview for minimized windows in other places, like
Alt-Tab and Expose.

I removed this preference two years ago mechanically, by removing all
the if statements, but never went through and cleaned up the code so
that windows are simply mapped for the lifetime of the window -- the
"architecture" of the old code that maps and unmaps on show/hide was
still there.

Remove this now.

The one case we still need to be careful of is shaded windows, in which
we do still unmap the client window. In the future, we might want to
show previews of shaded windows in the overview and Alt-Tab. In that
we'd also keep shaded windows mapped, and could remove all unmap logic,
but we'd need a more complex method of showing the shaded titlebar, such
as using a different actor.

At the same time, simplify the compositor interface by removing
meta_compositor_window_[un]mapped API, and instead adding/removing the
window on-demand.

https://bugzilla.gnome.org/show_bug.cgi?id=720631
2014-02-14 23:19:41 -05:00
..
Makefile.am doc: Fix file globs 2013-11-19 13:48:40 -05:00
meta-docs.sgml.in Remove theme.h and preview-widget.h from the API docs 2013-03-18 23:08:24 +01:00
meta-sections.txt Always map the client and frame windows 2014-02-14 23:19:41 -05:00
mutter-overview.xml Add overview and running sections to API docs 2013-03-14 18:07:05 -04:00
running-mutter.xml Add overview and running sections to API docs 2013-03-14 18:07:05 -04:00