Re: who "cleans" windows on withdraw?

[Matthias Clasen <maclas gmx de>]

> > > 
> > > I'm pretty positive that the programmer didn't want a maximized window
> > > to become a not-maximized but full screen, though, and I'd expect
> > > that to apply to "legacy" toolkits as well, so I'm not sure
> > > that cleaning _NET_WM_STATE makes sense.
> > > 
> > 
> > But anybody who reuses a withdrawn window, in a legacy toolkit or a 
> > modern one, would certainly check that the window size fits its new
> > purpose, wouldn't he ? Since the legacy toolkit propably doesn't have
> > the notion of maximized, the window would simply appear as a too large
> > one which needs to be resized before it can be reused. I don't see
> > a particular problem here. 
> 
> I guess I don't understand this concept of "reuse" ... do we have
> examples of an app that this concept applies to?

I only know this concept from the ICCCM. To find examples one would probably
have to grep for XWithdrawWindow though a large enough source tree of X
apps.

> (It's possible that we are only discussing dialogs, in which case
> the issue of maximization doesn't really matter much.)

I would expect dialogs to be the main examples of "hiding, but not
iconifying".

Matthias 

-- 
GMX - Die Kommunikationsplattform im Internet.
http://www.gmx.net