Re: proposed addition to EWMH: _NET_WM_NORMAL_GEOMETRY

> Nor do I see how adding a property that all WMs need to code around is
> less disruptive than an XMoveResize that lets them know the correct
> geometry without having to change anything at all.

I'm talking about disruptive for the user, not disruptive for the
programmer. The users are my priority here.

> And if a window can't handle being resized.. that's kind of funny. Are
> your users switching/restarting their WM multiple times a second?

Consider this example. You're watching a movie with a fullscreen
MPlayer. Your system receives a critical update to your window
manager, and it needs to restart. Which should happen: a) MPlayer
stays fullscreen and your window manager generally lets you focus on
the movie, or b) MPlayer resizes, you see a bunch of windows getting
reparented, and then MPlayer returns to fullscreen?

  Mark