Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!snorkelwacker!bloom-beacon!EXPO.LCS.MIT.EDU!rws
From: rws@EXPO.LCS.MIT.EDU (Bob Scheifler)
Newsgroups: comp.windows.x
Subject: Re: WM_STATE property
Message-ID: <9001031417.AA01694@expire.lcs.mit.edu>
Date: 3 Jan 90 14:17:29 GMT
References: <4966@uswat.UUCP>
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 29


    I cannot find any mention of WM_STATE in any of the header files
    under R3 or in the source code for uwm. Was it not implemented
    by uwm?

No, it wasn't.

    Is it used by any of the window managers?

Yes, by several ICCCM-friendly window managers in R4.  But note that the
ICCCM standard says "In general, clients should not need to examine the
contents of this property".  Only "utility" programs like xprop should
need to do this.

    Is there another way to determine if a window is iconified?

From the ICCCM standard (Section 4.1.4): "Once a client's non-override-redirect
top-level window has left Withdrawn state, the client will know that the window
is in Normal state if it is mapped, and that the window is in Iconic state if
it is not mapped.  It may select for StructureNotify on the top-level window,
and it will receive an UnmapNotify event when it moves to Iconic state, and a
MapNotify when it moves to Normal state."

    This is needed
    by a client other than the one that originally created the window
    of interest, so receiving an event won't work...

Another client can certainly select for StructureNotify events, but it can
also use XGetWindowAttributes for a one-shot look at the mapped state.