Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!elroy.jpl.nasa.gov!aristotle!pjs
From: pjs@aristotle.JPL.NASA.gov (Peter Scott)
Newsgroups: comp.windows.x.motif
Subject: Re: Deleting a whole list?
Message-ID: <1990Aug6.173153.6130@elroy.jpl.nasa.gov>
Date: 6 Aug 90 17:31:53 GMT
References: <1990Aug5.230646.9397@elroy.jpl.nasa.gov>
Sender: news@elroy.jpl.nasa.gov (Usenet)
Reply-To: pjs@aristotle.jpl.nasa.gov
Followup-To: comp.windows.x.motif
Organization: Jet Propulsion Laboratory, NASA/Caltech
Lines: 23
Nntp-Posting-Host: aristotle.jpl.nasa.gov

Since this particular case involved switching between only two lists,
both of which can be set up at compile time, I tried the following:

	list1 = XmCreateScrolledList (...) ;
	XtManageChild (list1);
	list2 = XmCreateList (XtParent(list1) ...);

	/* Add items to both lists  */

	In the list-switch callback, I unmanage the list that's 
currently managed, then manage the other one.  I have also tried
managing both lists, then unmanaging the one I don't want initially
after realizing the widget tree.

Unfortunately, this produces some extremely weird results; like two
scroll bars in the window, one shorter than the other; one of them
vanishes on the callback; one of the lists fills the scrolled window
with items whereas the other shows only one line and doesn't scroll...
ugly, ugly.  Surely the basic approach should work?  What am I missing?


This is news.  This is your       |    Peter Scott, NASA/JPL/Caltech
brain on news.  Any questions?    |    (pjs@aristotle.jpl.nasa.gov)