Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!usc!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: <9005081535.AA17821@lyre.MIT.EDU>
Date: 8 May 90 15:35:17 GMT
References: <4588@harrier.ukc.ac.uk>
Sender: daemon@athena.mit.edu (Mr Background)
Organization: DEC/MIT Project Athena
Lines: 18

> I haven't tried using
> a timeout callback, would that be much better?
>
> ... My UI builder requires a separate application context so that when a user
> is editing a translation table in a prototype he only picks up the Action routines
> available to the prototype and not those used internally by the builder.

Timeouts might improve things, but if you're not yet using them yet
you might be better served (:-) by performing your own select() calls
on the several display connections.  You'll need to do some linker
tricks to wrap XtAppAddTimeOut and XtAppAddInput in case a widget
uses them internally.  Or, if you can arrange to have all timeouts
and alternate input sources registered in 1 app context, simply register
the display connections from the other app contexts as alternate input
sources in the "master" app context.

But, when editing a translation table can't you simply filter out
the internal action routines explicitly?