Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!think!ames!mailrus!purdue!decwrl!sgi!daisy!klee
From: klee@daisy.UUCP (Ken Lee)
Newsgroups: comp.windows.x
Subject: Re: Window manager geometry updating.
Message-ID: <1527@daisy.UUCP>
Date: 26 Aug 88 16:50:18 GMT
References: <2783@pt.cs.cmu.edu>
Reply-To: klee@daisy.UUCP (Ken Lee)
Organization: Daisy Systems Corp., Mountain View, Ca.
Lines: 21

In article <2783@pt.cs.cmu.edu> healy@spice.cs.cmu.edu (James Healy) writes:
>Today I noticed that both twm and awm both do strange things with the x
>and y attributes of a window.  When I create a simple window and then map
>it while running either twm or awm, both set the x and y window attributes
>to weird values like 0 and 21.  These never get changed regardless of
>where I move the windows.

Many window managers, such as twm and awm, reparent windows so they can
include command banners.  The 0 and 21 you get are the window's
position relative to the new parent (the command banner is 21 pixels
thick).  They never change because you are moving the parent with the
window.  If you want position on the screen, get the position of the
parent (if it's not root) and add it to the 0 and 21.

Ken Lee
Daisy Systems Corp., Interactive Graphics Tools Dept.
-- 
uucp:  {ames!atari, ucbvax!imagen, nsc, pyramid, sgi, uunet}!daisy!klee
arpanet:  daisy!klee@sgi.com or daisy!klee@uunet.com

Don't applaud, just throw money.