Path: utzoo!mnetor!steve
From: steve@mnetor.UUCP (Steve Rees)
Newsgroups: comp.windows.x.motif
Subject: Re: to Myself (Scrollbars and other obcenities)
Message-ID: <5620@mnetor.UUCP>
Date: 6 Dec 90 14:02:22 GMT
References: <1990Dec3.004159.17177@bellcore.bellcore.com>
Reply-To: steve@mnetor.UUCP (Steve Rees)
Organization: Motorola Technical Systems Division, Toronto Design Centre
Lines: 24

In article <1990Dec3.004159.17177@bellcore.bellcore.com> rob@knopfler.leis.bellcore.com (Rob Herrera) writes:

[ basically on how to programmatically scroll a scrolledWindow widget ]...

>being managed by scrolled window A, use both XmScrollBarSetValues on the other 
>scrollbars (scrolled window B), and do an XtMoveWidget on the workarea 
>of scrolled window B, using the call_data->value passed down in
>XmScrollBarCallbackStruct.

Another, possibly cleaner way of getting the scrolled window to move is to:
1) Set the value resource on the B scrollbar, (as you say), and then
2) call XtCallCallbacks( scrollBar_B, XmNvalueChangedCallback, 
		XmScrollBarCallbackStruct )

	...where you fill in the appropriate fields in the callback struct
	(reason & value?).  It basically does the XtMoveWidget(), but this
	way you'll also activate any other callbacks which may normally get
	called on value change.  Make sense?

-- 
    Steve Rees
{uunet|utzoo}!mnetor!steve or (better) steve%mnetor.uucp@uunet.uu.net
Ma Bell: +1 416 475 8980  ext. 322
ISO-standard witty quote: "Quoth the raven, 'Eat my shorts!'" - Bart Simpson