Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!decwrl!sgi!daisy!klee From: klee@daisy.UUCP (Ken Lee) Newsgroups: comp.windows.x Subject: Re: Reparenting WM's Message-ID: <2637@daisy.UUCP> Date: 7 Feb 89 19:00:37 GMT References: Reply-To: klee@daisy.UUCP (Ken Lee) Distribution: comp Organization: Daisy Systems Corp., Mountain View, Ca. Lines: 21 In article pinkas@hobbit.intel.com (Israel Pinkas ~) writes: > >In porting this application, the power that be decided that the mechanism >we would use would be to raise the xterm from which the application was >invoked and display the text. (We use the WINDOWID environment variable to >determine the correct xterm.) According to the ICCCM (which is supported by the X protocol), only the window manager should be able to raise and lower top-level windows, such as xterm, unless they (anti-socially) request OverrideRedirect. Thus, you probably can't do what you want with existing window managers and clients (xterm). You might try, however, hacking a version of xterm that sets OverrideRedirect and forking this from your client. You can then manage this window as if it was a client sub-window. The user interface will be inconsistent with other clients, but that's the price of hacking. Ken Lee -- klee@daisy.uucp Daisy Systems Corp., Interactive Graphics Tools Dept.