Path: utzoo!utgpu!utstat!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!bloom-beacon!aardvark.umd.EDU!jonnyg
From: jonnyg@aardvark.umd.EDU (Jon Greenblatt)
Newsgroups: comp.windows.x
Subject: Awm enhancements/version number.
Message-ID: <8903291231.AA07480@aardvark.UMD.EDU>
Date: 29 Mar 89 12:31:24 GMT
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 59


	I am using AWM from the awm2.tar.Z file on expo. It seems this is
version 1.3 where as the older version from the distribution archive is
version 1.5. The only way to tell which is newer is to look at the revision
history. It seems TWM has the same version number problem. I don't like to
complain but I thought I would point this out in case other people are
having problems with this.

	AWM does not draw the grid box in a reasonable color for resize/move
operations on a color monitor. It is my opinion, I may be wrong, that GXxor
operations should only effect the first plane when drawing these types of
grid boxes. Right now I get a bearly visible yellow grid over white windows.
What I have done is changed this to use the first plane only and the result
is much more visible.
Here is the fix (the DRAW_PLANES value is confusing here and was not used):

*** awm.h.bak	Wed Feb 22 09:53:02 1989
--- awm.h	Tue Mar 28 09:30:04 1989
***************
*** 145,151 ****
  #define MAX_BOX_VECTORS		20
   
  #define DRAW_WIDTH		0 	/* use fastest hardware draw */
! #define DRAW_VALUE		0xfd
  #define DRAW_FUNC		GXxor
  #define DRAW_PLANES		1
  
--- 145,151 ----
  #define MAX_BOX_VECTORS		20
   
  #define DRAW_WIDTH		0 	/* use fastest hardware draw */
! #define DRAW_VALUE		0x1
  #define DRAW_FUNC		GXxor
  #define DRAW_PLANES		1
  

	I have found one other problem with awm that I have not been able to
fix thus far.  When selecting the Resize Gadget, awm assumes you are
resizing the upper right corner instead of letting you select the
edge/corner you wish to resize as with the f.resize operator.  In order to
fix the operation of the of the resize box, resizing might have to be
handled differently.  TWM does not have this problem but it handles resizing
completely differently.  Any suggestions?

	BTW My favorite window manager is UWM. I have recently taken interest
in TWM and AWM because I find they would be helpful in reducing the users
learning curve in a lab situation where they may only use X Windows for
a couple of projects. I find TWM to be the nicest in terms of both look and
feal. I have found AWM to be the most functional and much more robust. Since
TWM seems to ignore a lot of window manager hints, I find it to be somewhat
annoying to use. My choice for users is to run AWM but configure it as a
best I can as a UWM/TWM window manager. Since AWM alows you to configure it as
both a UWM and TWM look/feel alike it is the most versital. The main drawback
of AWM thought is the fact that it is so large, thats what happens when you
try to do everything.

						JonnyG.
					(jonnyg@rover.umd.edu)
					(jonnyg@umd5.umd.edu)