Path: utzoo!attcan!uunet!mcsun!inria!mirsa!modja.inria.fr!colas
From: colas@modja.inria.fr (Colas Nahaboo)
Newsgroups: comp.windows.x
Subject: Re: xterm windows height/width reported as height-1/width-1
Message-ID: <525@mirsa.inria.fr>
Date: 7 Feb 90 17:45:42 GMT
References: <47569@lll-winken.LLNL.GOV>
Sender: news@mirsa.inria.fr
Reply-To: colas@modja.inria.fr (Colas Nahaboo)
Organization: INRIA Sophia Antipolis
Lines: 27

In article <47569@lll-winken.LLNL.GOV>, casey@gauss.llnl.gov (Casey
Leedom) writes:
> 
>   I never received a response to this, so I'm trying again.  The R4 xterm
> saves height-1 and width-1 instead of height and width that the R3 xterm
> saved.  This causes uwm and xplaces to under report the size of xterms by
> one in each dimension.  I notice that twm does report the size
> correctly.  What's the story?  Is this new ICCCM behavior?

Yes, if you do a xprop on a R4 xterm, you see:

WM_NORMAL_HINTS(WM_SIZE_HINTS):
                user specified size: 578 by 340
                program specified size: 578 by 340
                program specified minimum size: 25 by 18
                program specified resize increment: 7 by 14
                program specified base size: 18 by 4

old (R3) WMs and clients use the "minimum size", but new (R4) WMs and
clients use the new ICCCM property "base size" for calculating the "logical"
size (pixel size  =  logical size  x  increment  + base size)

Moral: R3 WMs will give incorrect sizes for R4 clients.
One more reason to trash uwm :-)

Colas NAHABOO       BULL Research FRANCE -- Koala Project 
                    (GWM X11 Window Manager)  (colas@mirsa.inria.fr)