Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!stan!marvin!toml From: toml@marvin.Solbourne.COM (Tom LaStrange) Newsgroups: comp.windows.interviews Subject: Re: tvtwm and interviews Message-ID: Date: 14 Apr 91 15:12:35 GMT References: <1991Apr14.040956.5326@odin.corp.sgi.com> Sender: toml@Solbourne.COM (Tom LaStrange) Organization: Solbourne Computer, Inc. Lines: 24 In-Reply-To: linton@marktwain.rad.sgi.com's message of 14 Apr 91 04:09:56 GMT |> In article , toml@marvin.Solbourne.COM (Tom LaStrange) writes: |> |> > I don't have any objection to this, but when running under the tvtwm window |> |> > manager, the windows always wind up popping up over in the home corner of |> |> > the large "virtual" root window. |> |> |> |> It would appear that InterViews is setting USPosition hints. USPosition |> |> should only be set if the USER has asked for a window to be placed in a |> |> specific location. For program default positions, PPosition should be |> |> used instead. |> |> In the current implementation, by the time hints are set we don't know whether |> the placement is program-specified or via customization (command-line, Xdefaults, |> app-defaults). Setting USPosition is correct for the latter case (customization); |> the former shouldn't happen for top-level windows (at least, I can't see a reason |> why an application would do that). Transients are the one place where USPosition |> is technically wrong, but it seems like you would want window managers to put |> transients where the program wants anyway. I think program specified placement is common for multi top-level window applications where it is desired to have the top-level windows positioned relative to one another. -- (I kid you not)Tom LaStrange toml@Solbourne.COM