Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!samsung!uunet!mcsun!unido!fauern!tumuc!thsrem
From: thsrem@regent.e-technik.tu-muenchen.dbp.de (Thomas Schneider)
Newsgroups: comp.windows.x.motif
Subject: XtRemoveAllCallbacks in Destroy method
Summary: Is it necessary to call XtRemoveAllCallbacks in my destroy method ?
Keywords: XtRemoveAllCabacks, destroy method
Message-ID: <thsrem.651593472@tumuc>
Date: 25 Aug 90 14:11:12 GMT
Sender: news@tumuc.regent.e-technik.tu-muenchen.de
Lines: 26


Is it necessary to XtRemoveAllCallbacks for all callback types in
my wigdet destroy method ?

"X Toolkit Intrinsics - C Language Interface" X11R3 says in chapter
2.7:
In phase two, XtDestroyWidget performs the following on each entry
in the destroy list:
....
*  Recursively descends the tree and deallocates all pop-up widgets,
   constraint records, callback lists and, if the widget is a subclass
   of compositeWidgetClass, children.

On the other hand a lot of MOTIF widgets call XtRemoveAllCallbacks in
their destroy method, for instance ArrowB.c:
   XtRemoveAllCallbacks (aw, XmNactivateCallback);
   XtRemoveAllCallbacks (aw, XmNarmCallback);
   XtRemoveAllCallbacks (aw, XmNdisarmCallback);

Is this necessary ?

Thanks for clarification.
--
Thomas Schneider
/dev Software, Munich
UUCP: uunet!unido!tumuc!ths