Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!unmvax!polyslo!cosmos.acs.calpoly.edu!mike
From: mike@cosmos.acs.calpoly.edu (Mike Patnode)
Newsgroups: comp.windows.x
Subject: Re: XtReparentWidget (How about XtCopyWidget)
Keywords: How difficult to write
Message-ID: <9941@polyslo.CalPoly.EDU>
Date: 4 Apr 89 15:08:03 GMT
References: <8903300045.AA28710@metasoft.uucp>
Sender: news@polyslo.CalPoly.EDU
Reply-To: mike@cosmos.acs.calpoly.edu.UUCP (Mike Patnode)
Organization: Cal Poly Academic Computing Services, San Luis Obispo
Lines: 19

In article <8903300045.AA28710@metasoft.uucp> yong@metasoft.UUCP (Yongdeng Chen) writes:
>Hi there, ... (why I want to reparent a widget)

A very general, but hacked solution is to copy a widget into the new
location, and destroy the old one.  I've been working on a specific
CopyWidget routine which depends upon our program knowing about
all the attributes for each widget.

Before I reinvent the wheel, I was wondering if anybody already had some
sort of general XtCopyWidget routine which could copy an arbitrary
widget.  Any ideas on what this would involve.  Does the Toolkit contain
enough information in itself about each widget?  This would be a simple
solution to the reparent problem.

------------
Mike "Dodger" Patnode          | (n)   ..csustan!polyslo!mpatnode 
Yitbos Innovations Inc.        | (s)   ..sdsu!polyslo!mpatnode 
244 California Blvd            |         mpatnode@polyslo.CalPoly.EDU
San Luis Obispo, Ca  92630     | (805) 541-2048 / 543-9818 / 756-2516