Path: utzoo!dciem!nrcaer!scs!spl1!laidbak!att!pacbell!ames!mailrus!tut.cis.ohio-state.edu!bloom-beacon!ATHENA.MIT.EDU!swick
From: swick@ATHENA.MIT.EDU (Ralph R. Swick)
Newsgroups: comp.windows.x
Subject: Re: Mixing Widgets with non-widgets code (again)
Message-ID: <8806031159.AA09588@LYRE.MIT.EDU>
Date: 3 Jun 88 11:59:20 GMT
Article-I.D.: LYRE.8806031159.AA09588
References: <3755@pasteur.Berkeley.Edu>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: DEC/MIT Project Athena
Lines: 22


     Date:  2 Jun 88 23:12:14 GMT
     From:  pasteur!cory.Berkeley.EDU!dheller@AMES.ARC.NASA.GOV  (Dan Heller)

	...
     I tried ... having my own
     main loop use XNextEvent() and read events for both my window and
     the widgets window (I don't know why, but it doesn't seem to work).

You should be using XtNextEvent and dispatching all events to Xt
through XtDispatchEvent (because Xt is interested in certain events
regardless of the source window).  After the XtDispatchEvent, you can
then check to see if the event was really for one of your non-widget
windows.

	...
     The bottom line is: if you use widgets, can you ONLY use widgets
     and no more CreateWindow's?

The intent of the design is to allow mix-and-match when necessary.
We acknowledge that the rules for doing so need to be described in
more detail.