Path: utzoo!attcan!uunet!mcvax!unido!pcsbst!jkh
From: jkh@pcsbst.UUCP (jkh)
Newsgroups: comp.windows.x
Subject: re: Awm enhancements/version number.
Message-ID: <789@pcsbst.UUCP>
Date: 2 Apr 89 15:25:52 GMT
Reply-To: pyramid!pcsbst!jkh ( Jordan K. Hubbard )
Organization: PCS GmbH, Pfaelzer-Wald-Str. 36, 8000 Muenchen; West-Germany
Lines: 47

>	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.

This is incorrect. For at least a year now, awm's status has been
determined solely by its patch level. Since different source files are
checked in and out of RCS at each patch, it's impossible to judge
the "revision status" of awm as a whole by looking at one file, whether
or not it's "awm.c". The revision level of a particular file is only useful
for reporting bugs, and even then only in some cases. Look at patchlevel.h
for the real scoop on what you're running. Current patch level is 9.

>	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.

Thanks, I'll look these patches over. If they work fine on our color
system(s) (and Ardent's of course), they'll go into patch 10.

>	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.

This has been fixed by adding "constrained resize" Ala twm. I.E. Window
resizing does not start taking place until the cursor has left the
boundries of the window, allowing you to move it to any given anchor
point first.

This brings up a second point, which is that I'd be a lot happier if
people would just send such stuff to awm-bugs@ardent.ardent.com, or
to me (either way, it gets looked at properly). The proper addresses
are in the README file. Jon's complaint about version numbers is only
made worse by a lot of loose uncoordinated patches floating around, some
of which may break the "official" patches that I send out. Things are
already confusing enough with the two divergent releases already out there
(the R3 release and the recent comp.sources.x release, which I hope is
the "awm2.tar.Z file on expo).

Patch #10 will be released soon, so I'd suggest refraining from applying
Jon's patch (or at least keeping the original awm.h around) as it will
be included if it works properly.


		Thanks..