Path: utzoo!censor!geac!jtsv16!uunet!cs.utexas.edu!usc!bloom-beacon!EXPO.LCS.MIT.EDU!jim
From: jim@EXPO.LCS.MIT.EDU (Jim Fulton)
Newsgroups: comp.windows.x
Subject: Re: Consortium standard version of ICCCM now available
Message-ID: <8908021342.AA23331@expo.lcs.mit.edu>
Date: 2 Aug 89 13:42:05 GMT
References: <9740095@hpfclp.SDE.HP.COM>
Organization: X Consortium, MIT Laboratory for Computer Science
Lines: 33


	This indeed seems to be exactly what XIconifyWindow and 
	XWithdrawWindow do (excluding the WM_HINTS and map I mention for
	iconize below the initial description).  Does this mean that 
	XIconifyWindow will work whether the window is currently in 
	NormalState or WithdrawnState? If not, why not?

Nope.  The ICCCM requires you to track what state you are in (as a caveat, a
fair amount of care was taken to make sure that this wasn't too tough to do),
and Xlib reflects that.


	Why is there no XNormalizeWindow?

It was considered, but since we went to a lot of work to make a plain
XMapWindow be the trigger, we decided not to add another function which 
simply called XMapWindow.


	Finally, I noticed that the changes to the XSizeHints structure still
	refer to the type "int" even though it is not the same size on each
	machine.  I assume all these things called int are really supposed to
	be INT32 or something.  Is that true?

Not exactly.  The XSizeHints structure is a C language construct, not a 
network format.  The routines that manipulate the property copy the data
into the appropriate packets (actually array of longs which XChangeProperty
converts into CARD32's).  The real requirement is that the fields be large
enough to hold the appropriate type of value.


							Jim Fulton
							MIT X Consortium