Path: utzoo!attcan!uunet!peregrine!elroy.jpl.nasa.gov!sdd.hp.com!think.com!mintaka!bloom-beacon!LARRY.MCRCIM.MCGILL.EDU!mouse
From: mouse@LARRY.MCRCIM.MCGILL.EDU
Newsgroups: comp.windows.x
Subject: Re:  Problem with window placement
Message-ID: <9012010643.AA02102@Larry.McRCIM.McGill.EDU>
Date: 1 Dec 90 06:43:33 GMT
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 27

> Previously I posted a message about being unable to configure windows
> with dimensions greater than MAXSHORT (on a Sun SPARCstation 1).  I
> have since discovered that my problem is not in configuring the large
> parent window but placing the children of the large window at X and Y
> positions greater than MAXSHORT.  If I attempt to do this the
> ConfigureNotify events for both the parent and the child report that
> the window was positioned at negative values for any value larger
> than MAXSHORT

> what I am doing is basically as follows:
> 1) configure the parent window with width + height at MAXINT
> 2) configure a child of that window at x & y values of 253 & 32797
> 3) when I receive a ConfigureNotify event for the child the values
>    reported back form the server are 253 & -32739

The protocol uses signed 16-bit values for window positions.  Not much
you can do about it.

But, why do you want to do this?  You may be trying to solve a problem
the wrong way.  (I've often seen someone ask "how do I do <foo>" when
the answer is "you can't", but they really meant "how do I do <bar>"
and have mistakenly decided that <foo> is the only way to get <bar>.)

					der Mouse

			old: mcgill-vision!mouse
			new: mouse@larry.mcrcim.mcgill.edu