Path: utzoo!attcan!uunet!lll-winken!csd4.milw.wisc.edu!mailrus!purdue!bu-cs!bloom-beacon!EXPO.LCS.MIT.EDU!kit
From: kit@EXPO.LCS.MIT.EDU (Chris D. Peterson)
Newsgroups: comp.windows.x
Subject: Re: breaking out of XtMainLoop()
Message-ID: <8904191907.AA05497@expo.lcs.mit.edu>
Date: 19 Apr 89 19:07:19 GMT
References: <44097@tut.cis.ohio-state.edu>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 17


>  Now that I have obtained
> a value, I want to exit the Mainloop, without destroying the windows,
> so that I can change the list and restart the mainloop. 

Paul has explained how to code your own XtMainLoop() and this is certainly
a valid thing to do.  My question is why not just change your list in the
callback proceedure?  I have been writing toolkit programs for almost 
2 years now, and have only once had to code my own XtMainLoop().  I guess
this is just a general caution to all you toolkit developers out there to
look before you leap.  Please take a minute to try to work within the
framework provided before you dive into building your own Event Dispatcher.


                                                Chris D. Peterson
                                                MIT X Consortium