Path: utzoo!attcan!uunet!cs.utexas.edu!usc!bloom-beacon!ATHENA.MIT.EDU!swick
From: swick@ATHENA.MIT.EDU (Ralph R. Swick)
Newsgroups: comp.windows.x
Subject: Re: XSetNormalHints behaviour
Message-ID: <8906291711.AA02240@LYRE.MIT.EDU>
Date: 29 Jun 89 17:11:50 GMT
References: <8906261820.AA00989@galapas.ai.mit.edu>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: DEC/MIT Project Athena
Lines: 15


     Date:  Mon, 26 Jun 89 14:20:16 EDT
     From:  jla@ai.mit.edu (Joseph Arceneaux)

     A couple of months ago I ran into the problem of consecutive calls to
     XSetNormalHints obliterating the values I'd established in previous
     calls.

It is definitely the case that XSetNormalHints replaces the entire
window property, not merely the fields flagged in the current call.
If you can't remember the original values, you'll have to query
them as you show in your example code.

This is documented in the Xlib specification, Chapter 9.
Page 277 in the Digital Press bible.