Path: utzoo!attcan!uunet!cs.utexas.edu!usc!bloom-beacon!bsw.UUCP!adam
From: adam@bsw.UUCP (Adam R de Boor)
Newsgroups: comp.windows.x
Subject: R2 vs. R3 VPaned widget geometry manager...
Message-ID: <8907191304.AA02691@tellurium.bsw.com>
Date: 19 Jul 89 13:04:11 GMT
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 19

In the R2 VPaned widget, if I had a pane whose allowResize resource was true
and that pane issued a resize request, rather than resizing the whole
vpaned object, it would resize the requesting pane, then grow or shrink a
nearby pane to match. Under R3, the shell just resizes itself to accomodate the
new pane, which isn't what I want (frequently, even when the shell does
resize itself, the requesting pane doesn't actually resize -- some other pane
does).

(a) why did this change
(b) is there any way to get the R2 behaviour?

I'll even accept an answer along the lines of: In R4, the VPaned geometry
manager will perform XtQueryGeometry calls, setting the CWHeight bit and
passing the height it would like to make a pane, dealing with the result and
finally adjusting all the panes to accomodate a request from an allowResize
pane, only asking the shell to make it bigger if it comes up against some
hard limit (like all other panes are at their min size).

a