[comp.archives] [xpert] "fixed" vtwm

thoth@reef.cis.ufl.edu (Gilligan) (08/26/90)

Archive-name: vtwm/25-Aug-90
Original-posting-by: thoth@reef.cis.ufl.edu (Gilligan)
Original-subject: "fixed" vtwm
Archive-site: cis.ufl.edu [128.227.224.1]
Archive-directory: /pub/fract
Reposted-by: emv@math.lsa.umich.edu (Edward Vielmetti)


  Here at UF we have fixed all the simple bugs in vtwm including the
"moving_icon" and the raiselower/lower bug.
  A patch for the moving_icon bug was posted earlier to this group by
Steve Beaty and is (to my knowledge) perfectly correct.  It happens to
be the way we fixed it.
  The raiselower/lower bug can be demonstrated by "f.lower"ing a
window.  Its virtual window does NOT lower.  f.raiselower has a
similar problem.
  I don't have a patch for the xmh simplemenu problem and I have a
sneaking suspicion that it might be Xmh's fault.

  Our patched source can be "ftp"ed from cis.ufl.edu in pub/fract (the
only directory I can write to right now).  I have sent mail to the
author but he's gone till september.  Once I can talk to him we can
merge our changes onto his source and maybe it can become official

  Vtwm IS slower than twm.  It has more data to keep track of.  The
main thing that bothers me is the time it takes our servers to move
all the windows, and I have to make empty "streets" to "drive" down
when I'm moving from workspace to workspace because the cost of expose
events.  Even if you don't expose windows you can slow your machine
down with sheer numbers.  An xpostit farm off in the corner can make a
REAL difference.
  I use a color Sun 3/80.  When I can use a Sun SS1+ I don't have to
worry about speed any more because the 1+ is much to fast to be slowed
down by some piddly expose events and text drawing.  Ahh, what I
wouldn't do for a color Sparc on my desk.
--
/--------------------
"a window is a terrible thing to paste" -me
( My name's not really Gilligan, It's Robert Forsman, without an `e' )
--------------------/