Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uwm.edu!zaphod.mps.ohio-state.edu!usc!snorkelwacker!bloom-beacon!EXPO.LCS.MIT.EDU!converse
From: converse@EXPO.LCS.MIT.EDU
Newsgroups: comp.windows.x
Subject: Re: Athena Viewport Widget behaviour (bug?)
Message-ID: <9007202218.AA07193@excess.lcs.mit.edu>
Date: 20 Jul 90 22:18:15 GMT
References: <RICK.90Jul20163950@brodie.cstr.ed.ac.uk>
Sender: daemon@athena.mit.edu (Mr Background)
Organization: X Consortium, MIT Laboratory for Computer Science
Lines: 33


> Now, when the Viewport gets a geometry request from its child, it checks to
> see if the request is allowable. If so, it checks to see whether the new
> value is greater than the previous one. If it is, it shrinks the child by the
> space needed to display a scrollbar. It does this *without checking to see if
> the scrollbar is already displayed*.
> 
> This seems broken to me. Firstly, it should check to see if the scrollbar is
> displayed (not difficult). 

Please fill out a bug report template in doc/bugs/bug-report, preferably 
with a sample fix, and send it in.  With a quick check of adding various
folders to my xmh, and watching the area where buttons are displayed, I 
don't see the behavior that you describe.  I can add lots of rows of new
folder buttons, and the Box which contains the buttons, which is a child of
the Viewport, never appears to shrink after the vertical scrollbar is created.


> the Viewport should adjust its
> own size to allow for the scrollbar rather than shrinking its child.

Are you suggesting that when a Viewport decides it needs a new scrollbar,
it should make a geometry request of it's parent?  That seems okay, but
if the parent denies the request, what else is there to do but shrink
the child of the Viewport?  

Using resources, you can force the scrollbars to always (or never) appear.
If you force the scrollbars never to appear, the child's geometry requests
will propagate to the Viewport's parent.  Isn't that what you want?


Donna Converse
converse@expo.lcs.mit.edu