Path: utzoo!yunexus!hydroesm!jtsv16!torsqnt!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!mcsun!inria!seti!bdblues.altair.fr!didier
From: didier@bdblues.altair.fr (Didier Plateau)
Newsgroups: comp.windows.x
Subject: Postponed widget destruction with  XtDestroyWidget
Keywords: XtDestroyWidget
Message-ID: <862@seti.inria.fr>
Date: 29 May 90 13:53:28 GMT
Article-I.D.: seti.862
Sender: news@seti.inria.fr
Reply-To: didier@bdblues.altair.fr
Organization: Altair
Lines: 25

using Xt and Xm.

  Assume we want to cut the widget W0 with parent WP0 and paste it to
replace the 
  widget W1 with parent WP1.
  The algorithm consists in destroying W0, destroying W1, and building a
copy a W0
  hooked to WP1.

To destroy the W0 and W1 widgets, we use the Xt primitive
"XtDestroyWidget" which marks
the widgets as destroyed but postpone the effective destruction until
the next event.
Therefore, WP1 cannot receive a new child widget until the destruction
is effective.
To solve this problem, we are thinking of generating an application
event and perform
the copy when processing this event.

Does anybody know any cleaner solution to deal with this problem ? Any
advice will be welcomed ... 

  Thanks in advance,
       Didier Plateau,
           Altair