Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!think!paperboy!snorkelwacker!mit-eddie!uw-beaver!Teknowledge.COM!unix!hplabs!hp-pcd!hpcvlx!ben
From: ben@hpcvlx.cv.hp.com (Benjamin Ellsworth)
Newsgroups: comp.windows.x
Subject: Re: R4 Athena Widget question.
Message-ID: <100920177@hpcvlx.cv.hp.com>
Date: 27 Feb 90 18:38:16 GMT
References: <1990Feb24.002324.14813@agate.berkeley.edu>
Organization: Hewlett-Packard Co., Corvallis, OR, USA
Lines: 29


OK, I give.  The twists and turns of this thread have confused me.

Is the question "How to destroy a widget hierarchy?"

If you want to destroy a widget and all of its children you call
XtDestroyWidget.  Due to some funky-ness in the Xt implementation you
sometimes have to handshake an event through, but XtDestroyWidget will
destroy the widget and (if the widget was written correctly) all of the
private data associated with the widget.  What's so hard about that?

Is the question "How do you exit an Xt application?"

My personal favorite is "exit(0);"  This is UN*X and exit has well
defined behavior on all systems that I'm familiar with.  I suppose that
if one was particularly paranoid one could destroy all widget
hierarchies, then destroy all app contexts, and then exit.  What's hard
about that?

Of course, I could have missed the point entirely...

-----------------------------------------------------------------------
Benjamin Ellsworth      | ben@cv.hp.com                | INTERNET
Hewlett-Packard Company | {backbone}!hplabs!hp-pcd!ben | UUCP
1000 N.E. Circle        | (USA) (503) 750-4980         | FAX
Corvallis, OR 97330     | (USA) (503) 757-2000         | VOICE
-----------------------------------------------------------------------
                     All relevant disclaimers apply.
-----------------------------------------------------------------------