Path: utzoo!attcan!uunet!husc6!bloom-beacon!godzilla.ele.toronto.EDU!moraes
From: moraes@godzilla.ele.toronto.EDU (Mark Moraes)
Newsgroups: comp.windows.x
Subject: Re: v00i002:  Ardent Window Manager(X11), Part01/13
Message-ID: <8808120614.AA26794@godzilla.ele.toronto.edu>
Date: 12 Aug 88 03:34:41 GMT
References: <4961@pasteur.Berkeley.EDU>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: EECG, University of Toronto
Lines: 36

In article <4961@pasteur.Berkeley.EDU> pasteur!cory.Berkeley.EDU!dheller@ames.arc.nasa.gov (Dan Heller) writes:
>                                  however, I'd love to get feedback
>on other people's experiences with awm and/or other window managers.
>I haven't run TWM, but I haven't seen many bug reports on it... is
>that cuz no one uses it, or cuz it's bugless? :-)

I've been using twm ever since version 1.0 - for the record, I think
its been getting better with every release, and is still small (little
over half the size of awm), and reasonably functional.

There are two bugs in twm that annoy - one sounds like what you report
for awm:
>If I write a program which has a simple form widget and some command
>wigets in it and I use my mouse button within the _form_ widget, AWM
>seems to think I'm on my _root_ window and tries to translate events
>ignoring the fact that I'm not on my root window...

twm does the same for popup widgets - when you set override-redirect -
which makes it kind of hard to use dialogs - your keystrokes go into
never-never land, or the root window to be more precise. I've tried to
track this down, but haven't been able to find this. As far as I can
tell, twm has no idea that the override-redirect window is there, and
isn't involved in any way - but it still seems to get events that have
the Root Window as the window field. I'm not sure why this happens -
does anyone have a fix/reason for this behaviour?

The other bug is that it doesn't deal with zaphod mode (dual screen)
on color Suns. It works fine on one screen, but doesn't allow anything
to happen in the other screen even if you run another wm there - two
awms are fine and two uwms also fine. Since I only use the mono screen
anyway, it doesn't matter usually. But when I want to test something
in color......

Otherwise I'm quite happy with it - doesn't dump core very much, and
since version 3.2, doesn't die too often when an application dies
abruptly.