fontforge/fontforge — pull request #749 by Oblomov (2013-09-14 14:57:41+00:00)
Title: Follow ICCCM spec when hiding windows

In some non-reparenting window managers such as Awesome 3.4, FontForge
dialogs behave incorrectly. The symptoms are the following:

* on first use, the dialogs are visible
* when closed and reopened, they are not visible anymore
* switching to a different tag/workspace and then back makes all
previously opened dialogs visible again (even the ones that were not
reopened).

This is caused by the WM not noticing the withdrawal of the dialogs by
FontForge, which in turn is caused by FontForge not complying with the
ICCCM specification, section 4.1.4[1], which recommends sending a
synthetic UnmapNotify event to the root screen when unmapping a window.

[1]: http://tronche.com/gui/x/icccm/sec-4.html#s-4.1.4

Since this behavior is needed often, Xlib provides the XWithdrawWindow()
to unmap and send the event with a single call.

This patch fixes the issue with FontForge in Awesome 3.4 by replacing
calls to XUnmapWindow() with XWithdrawWindow() for top-level windows.