Path: utzoo!attcan!uunet!cs.utexas.edu!usc!bloom-beacon!EXPO.LCS.MIT.EDU!kit
From: kit@EXPO.LCS.MIT.EDU (Chris D. Peterson)
Newsgroups: comp.windows.x
Subject: Re: Reparenting Widgets
Message-ID: <8907061538.AA04493@expo.lcs.mit.edu>
Date: 6 Jul 89 15:38:54 GMT
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 16


> O.K. then, how about a XtCopyWidget() ?  This would simply (sic) the operation
> greatly for those who are trying to do it, as well as reparenting.

I remain unconvinced.  Since this will probabally be slower than creating
a new widget, why is it useful?  You should already have a routine
lying around your application that creates this widget, I don't see
any advantage of XCopyWidget() over just calling that piece of application 
code again to recreate the widget.  

						Chris D. Peterson     
						MIT X Consortium 

Net:	 kit@expo.lcs.mit.edu
Phone:   (617) 253 - 9608	
Address: MIT - Room NE43-213