Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!usc!snorkelwacker!apple!uokmax!servalan!rmtodd
From: rmtodd@servalan.uucp (Richard Todd)
Newsgroups: comp.windows.x
Subject: Re: Trouble with tvtwm (Bug?)
Message-ID: <1990Sep3.213711.2240@servalan.uucp>
Date: 3 Sep 90 21:37:11 GMT
References: <1990Sep3.131517.28047@batcomputer.tn.cornell.edu> <1440@ruunsa.fys.ruu.nl>
Organization: Ministry of Silly Walks
Lines: 42

muts@fysaj.fys.ruu.nl (Peter Mutsaers /100000) writes:
>#I've started using Tom LaStrange's new tvtwm, and (except for the nasty 
>#things it does to this poor little sparcstation 1+.... swap, swap, swap...

>Strange, I run it on an Apollo 2500 with 8Mb, and I notice no performance
>difference with twm, while using some xterms too.
>Is tvtwm really supposed to be using so much more memory than twm?

 Tvtwm itself doesn't seem to more memory than twm.  However, creating the
window for the virtual desktop causes the X *server* to eat up more memory
(on my Mac IIx, the X server now seems to be running ~4.9M versus ~3M.  Of
course, this is a color server; it's not surprising that storage for a 
1400x1400x8 bit window takes up a good deal of room...)  My experience is that
as long as you don't have windows taking up more of the desktop than the 
"real desktop" space (640x480 pixels in my case) you won't notice a difference
in performance; the memory for the rest of the virtual desktop stays paged
out and doesn't bother anyone.  If you start putting stuff on other portions
of the virt. desktop, the system thrashes more heavily.

>#However, I've been having some trouble with resizing windows.  When I try 
>#to resize a window, xterm for example, the window explodes to some `
>#ridiculous size as soon as I click on the resize box.  For example, if

>#I only have this problem when I'm away from the upper left hand corner
>#of the virtual root window.  So what I end up doing to resize is
>#f.scrollhome, drag the window there, resize it, put it back where
>#it used to be, pan over there, and go back to work.  Kind of a nuisance.

Yep, I've noticed this bug too.  It seems to be a problem in resize.c, where
the code for handling the mouse motion is passing the mouse coordinates
on the real root window, but the code seems to be treating them as if they
were coordinates on the virtual desktop.  Alas, I really don't understand this
code well enough to come up with a way to fix it... 

Another workaround is to, instead of clicking on the resize box, to resize
your windows by selecting a menu item that does f.resize from the Twm menu.
Alas, the nice outline of the window you see as you resize disappears (I think
it's being put in the upper left hand corner of the virt. desktop), but at
least your window size doesn't get adjusted to absurd values.
--
Richard Todd	rmtodd@uokmax.ecn.uoknor.edu  rmtodd@chinet.chi.il.us
	rmtodd@servalan.uucp