Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!decwrl!shelby!bloom-beacon!HARVARD.HARVARD.EDU!jimf%saber
From: jimf%saber@HARVARD.HARVARD.EDU
Newsgroups: comp.windows.x
Subject: Re: cleaning up from exit
Message-ID: <9003091424.AA26239@armory>
Date: 9 Mar 90 14:24:28 GMT
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 20

|>> XtAddCleanUpProc(routine, client_data)
|>> XtRemoveCleanUpProc(routine, client_data)

|You might want to make this a more general solution.  Add the notion of
|interposition to the Xt intrinsics as XView does.

He's right, interposition is a much more general solution.  I suggest,
however, *NOT* having an interposition call for each of the events
that you want to interpose on.  The SunView/XView method, which has
generic event interposers, destroy interposers, and others (five or
six in all, I can never remember and the manuals are junk) is
overcomplex.  It would have been better to have a single interposer
and key off event types (which you have to do ANYWAY) instead of five
or six of them.

Happy hacking,

jim frost
saber software
jimf@saber.com