Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!uwm.edu!wuarchive!sdd.hp.com!elroy.jpl.nasa.gov!thyme!kaleb
From: kaleb@thyme.jpl.nasa.gov (Kaleb Keithley)
Newsgroups: comp.windows.x.motif
Subject: Re: How to re-manage the same child widget
Message-ID: <1991May16.154512.23319@thyme.jpl.nasa.gov>
Date: 16 May 91 15:45:12 GMT
References: <9105132043.AA11128@11128> <91May15.224003edt.8838@orasis.vis.toronto.edu>
Distribution: inet
Organization: Jet Propulsion Laboratory, Pasadena, CA
Lines: 22

In article tjhorton@vis.toronto.edu ("Timothy J. Horton") writes:
>jerryl@is.Morgan.COM (Jerry Liebelson) writes:
>>  QUESTION:  Is there an efficient, trouble-free way to unmanage and re-manage
>>once instance of this XmList under different parent container widgets, which
>>themselves might be contained within different shell widgets?
>
>XtReparent (I think that's what it's called -- no books nearby).

This fits into the category of dis-information.  There is no XtReparent().
And there is no easy, nor clean way to reparent widgets.  This is not my
opinion, but an echo of something Schliefer/Gettys/Converse/et. al. have
said in months gone by.

One possible solution would be to GetValues() the XmNitems resource from 
one and SetValues() it onto the other.  Since this is fast and simple, 
it's the way I would go.

-- 
Kaleb Keithley                        kaleb@thyme.jpl.nasa.gov

Meep Meep                             Roadrunner
Veep veep                             Quayle