Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!ub!boulder!stan!ninja!toml From: toml@ninja.Solbourne.COM (Tom LaStrange) Newsgroups: comp.windows.x Subject: Re: tvtwm ideas Message-ID: <1990Sep10.191838.27419@Solbourne.COM> Date: 10 Sep 90 19:18:38 GMT References: Sender: news@Solbourne.COM Reply-To: toml@solbourne.com Organization: Solbourne Computer, Inc. Lines: 72 (Many generic twm requests deleted) |> o We should have more control over the monochrome colors in the panner - |> in color it's possible to specify what the colors of the panner analogs |> of certain windows are, so it should be possible to specify different |> grayscales too. Right now the panner is just a big black blob. The small "virutal" have the same background and border colors as the window frames. Perhaps your background and border colors are specified to be the same? |> o Another way to make the panner entities more legible in monochrome would |> be to be able to control the color of their borders. I suppose this is |> because of my particular init file, but in my panner, icons are drawn as |> black boxes with white outlines, but all other windows are drawn as black |> boxes with black outlines. Ick. See my previous comment. |> o Icon manager windows should be of resource class "Twm" instead of |> "Untitled" so that I can talk about all Twm-produced windows in one |> expression. I agree. |> o I think it would be cool if you could configure it so that click-drag on |> the root window scrolled the desktop. Scrolling the whole bitmap would |> probably be too slow, but a realtime pan of the window outlines should be |> possible. |> |> o sometimes tvtwm picks a window and makes it be roughly 100x100 after |> mapping it. I've seen it happen to xterms, emacses, and xview windows - |> it will draw the outline of the window waiting for me to click, but |> whether I just click left or select a different size, it maps it too |> small. Now, it seems to only want to do this to one window at a time - |> if I launch several xviews in the background, the first will often have |> this weirdness happen, but the others don't. It doesn't only happen |> when creating windows but also sometimes when deiconifying them. Has |> anyone else seen this? This sounds like one I may have just fixed. Try this unofficial patch: *** old/vdt.c Thu Sep 6 12:54:23 1990 --- vdt.c Thu Sep 6 12:54:29 1990 *************** *** 259,265 **** TwmWindow *tmp_win; { XUnmapWindow(dpy, tmp_win->frame); ! XUnmapWindow(dpy, tmp_win->w); if (tmp_win->virtualWindow && !tmp_win->sticky) XUnmapWindow(dpy, tmp_win->virtualWindow); } --- 259,266 ---- TwmWindow *tmp_win; { XUnmapWindow(dpy, tmp_win->frame); ! if (!tmp_win->iconmgr) ! XUnmapWindow(dpy, tmp_win->w); if (tmp_win->virtualWindow && !tmp_win->sticky) XUnmapWindow(dpy, tmp_win->virtualWindow); } -- Tom LaStrange Solbourne Computer Inc. ARPA: toml@Solbourne.COM 1900 Pike Rd. UUCP: ...!{boulder,sun}!stan!toml Longmont, CO 80501