Path: utzoo!attcan!uunet!cs.utexas.edu!usc!bloom-beacon!ATHENA.MIT.EDU!swick
From: swick@ATHENA.MIT.EDU (Ralph R. Swick)
Newsgroups: comp.windows.x
Subject: Re: ApplicationContext and Multple Displays
Message-ID: <8906301352.AA03018@LYRE.MIT.EDU>
Date: 30 Jun 89 13:52:16 GMT
References: <062889.140247.msacks@ibm.com>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: DEC/MIT Project Athena
Lines: 27

oops, blush; somebody else made the coffee this morning.
Sorry 'bout that completely bogus message a few minutes ago.

Your test case also works for me when I simply refer to
a screen that my particular display understands:

***************
*** 157,163 ****

      /* create two top level shells, one on each screen */
      /* come up on screen one of my machine */
!     scrn = ScreenOfDisplay(dpy1, 1);

      num_args=0;

--- 158,164 ----

      /* create two top level shells, one on each screen */
      /* come up on screen one of my machine */
!     scrn = ScreenOfDisplay(dpy1, 0);

      num_args=0;

but you're actually failing due to a known bug in Xt.  If your
two screens have different depths you'll win, otherwise you
have a high probability of failing unless the two servers happen
to be running very similar code.  There is no convenient work-around.