On Fri, Sep 05, 2014 at 09:36:42PM +0100, Dominik Vogt wrote:
> (All these questions aim at finding out exactly what the
> WindowShade command does on your system, and what the difference
> is between shading and resizing windows manually.)
It's to do with EWMH_SetWMState() -- that's the only difference, and
indeed in terms of CMD_WindowShade(), not calling that won't refresh the
contents.
The call-chain looks like this:
EWMH_SetWMState() -> ewmh_ChangeProperty() -> XChangeProperty()
I do not know why, in the case of the XChangeProperty() call happening
and fvwm receiving the PropertyNotify event for the EWMH-class of
events (it's not just windowshade, sticky also makes the window work
correctly), that the window is then magically refreshing its contents
and returning to normal.
That really is the culprit here---and indeed, WindowShading is no
different to resizing anyway, and having spent a while trying to debug
this, I can only conclude fvwm isn't to blame, nor do I want to dig
around in Chrome's internals.
-- Thomas Adam
--
"Deep in my heart I wish I was wrong. But deep in my heart I know I am
not." -- Morrissey ("Girl Least Likely To" -- off of Viva Hate.)
