Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!sdd.hp.com!zaphod.mps.ohio-state.edu!brutus.cs.uiuc.edu!apple!snorkelwacker!bloom-beacon!ATHENA.MIT.EDU!swick
From: swick@ATHENA.MIT.EDU (Ralph Swick)
Newsgroups: comp.windows.x
Subject: Re: Multiple Application Contexts
Message-ID: <9005071732.AA17014@lyre.MIT.EDU>
Date: 7 May 90 17:32:52 GMT
References: <9004261750.AA24717@expo.lcs.mit.edu>
Sender: daemon@athena.mit.edu (Mr Background)
Organization: DEC/MIT Project Athena
Lines: 17

> (kit)
> I
> will argue that it is more trouble that it is worth.

And a bit of trouble it will be, too.  The most immediate problem
will be deciding how to multiplex events/inputs/timers across
several app contexts.  Probably, you'll wind up polling using
XtAppPending() and XtAppProcessEvent().

I could invent a reason or two why a single process might want more
than one app context, but since Andy didn't give any details I wonder
if he found a good reason - Andy?

Also, at least one thing that sounds like maybe it should be
independently specifiable across app contexts within a single
process isn't.  The  case that readily jumps to mind is error
and warning handlers.