home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cs.utexas.edu!natinst.com!news.dell.com!texsun!cronkite.Central.Sun.COM!west.West.Sun.COM!news2me.EBay.Sun.COM!seven-up.East.Sun.COM!marley.Eng.Sun.COM!ama
- From: ama@marley.Eng.Sun.COM (Al Amaral - SunSelect)
- Newsgroups: comp.windows.x
- Subject: Re: Writting to other client`s windows.
- Message-ID: <1iif8uINNiuu@seven-up.East.Sun.COM>
- Date: 7 Jan 93 23:44:30 GMT
- References: <251@io.trident.datasys.swri.edu>
- Organization: Sun Microsystems Inc. - BDC
- Lines: 27
- NNTP-Posting-Host: marley.east.sun.com
-
- In article <251@io.trident.datasys.swri.edu> johns@io.datasys.swri.edu (Stephen Johns) writes:
- >I have two clients, via sockets I send the window ID from one client
- >to the other. I then try XDraw calls to the passed window ID. Nothing
- >happens, and I mean nothing, no warning, no errors, no drawing. Does
- >X support this at all?
-
- Yes, this is supported. Did you flush your X dpy buffers? Calling
- XSync, XFlush, or most of the XEvent routines will do this for you.
-
- The only two things (that I can think of at the moment) you have to
- watch for is:
-
- 1) If your clients are not on the same machine you have to make sure
- that different byte ordering is taken into consideration when you
- pass the window ID through the socket. If this was your problem
- you would get an error...
-
- 2) If the client which created the window goes away the window will,
- by default also go away. The other client had better watch for this.
- There is supposed to be a mechanism for asking the server to keep
- things like windows around after the client has closed its connection,
- but I've never used it so I don't know off-hand what it is.
-
-
- --
- --------------------------------------------------------------
- Al Amaral Al.Amaral@East.Sun.COM
-