Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!rpi!ispd-newsserver!ism.isc.com!emisle!dvb From: dvb@emisle.uucp (David Van Beveren) Newsgroups: comp.windows.x Subject: Re: R5 wish list (was Re: Reattachable X clients) Message-ID: <1991Mar17.234456.456@emisle.uucp> Date: 17 Mar 91 23:44:56 GMT References: <19910301203957.6.BARMAR@OCCAM.THINK.COM> <17895@lanl.gov> Reply-To: dvb@emisle.UUCP (David Van Beveren) Organization: Emerald Isle Systems, Ltd. Agoura Hills, CA Lines: 42 In article <17895@lanl.gov> dlc@c3.lanl.gov (Dale Carstensen) writes: > >|> In article <19910301203957.6.BARMAR@OCCAM.THINK.COM> barmar@think.COM (Barry Margolin) writes: >|> >|> > I'd >|> > like to be able to move my X clients from one display to another (for >|> > instance, if I had a home X terminal I'd want to bring my windows home >|> > with me), or reboot my workstation without having to kill all the remote >|> > X clients (saving local clients across reboots is outside the scope of >|> > X). X clients communicate with their server via a "display" abstract >|> > data type; this object hides the details of the communication protocol, >|> > allowing the same clients to work over TCP, DECnet, shared memory, etc. >|> > Thus, it should be possible for them to disconnect themselves from the >|> > transport mechanism completely, and later open a new transport >|> > connection and use that. How about the ability to move widgets from one display to another. This would imply that all descendants would be moved as well. Obviously right now I could destroy a widget, and create a new one under a different context which is on a different display, but re-parenting an existing widget to a context on a different display would be nicer. An example of a use of this: I have an X program which is a server for a graphics engine. Only one client can have the server at as time. When a client's request for service is acknowledged (communication is via sockets), a blank graphics palatte is drawn on the client's display, which was passed as part of the request. The server maintains a cache of open displays. If a display not in the cache is requested, an XOpenDisplay occurs, and an application context is created for that display. Now, Currently I have to destroy the palette on the last used display, and create a new one on the new display. If I could move the palette instead, things would be simpler. (The palette is a set of sliders, scrollbars, menus, etc around a drawing area. It contains about 30 widgets altogether.) The ability to move windows from one display to another could also be useful in some situations. -- David Van Beveren INTERNET: emisle!dvb@ism.isc.com EIS ltd. Professional Software Services UUCP: ..uunet!emisle!dvb voice: (818) 587-1247