Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!snorkelwacker!apple!agate!ucbvax!us.oracle.com!kmclough.US2.oramail
From: kmclough.US2.oramail@us.oracle.com ("kmclough.US2")
Newsgroups: comp.windows.x.motif
Subject: app defined scrolling in 1.1
Message-ID: <9010171951.AA15697@dvlseq.us.oracle.com>
Date: 17 Oct 90 19:51:26 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: inet
Organization: The Internet
Lines: 19


Aaarrrgggh! Why did OSF change the ScrolledWindow code in 1.1 so that
you have to set visualPolicy to XmVARIABLE when scrollingPolicy is
XmAPPLICATION_DEFINED? For that matter, what is the point of XmVARIABLE
layout to begin with!? It seems contrary to the whole purpose for the
existence of a scrolled window to have it grow to match the size of the
work area.

Is it so weird to want a fixed-size clip window, but not to want scrollbars
on it (for instance, because you're using one scrollbar to scroll two windows
simultaneously)?

Am I missing the point, or something?


------------------------------------------------------------------------------
Kevin McLoughlin
Oracle Corporation
kmclough@oracle.com