From: mackay@ATHENA.MIT.EDU
Message-Id: <8911012144.AA26730@E40-368-1.MIT.EDU>
To: argus2@ATHENA.MIT.EDU
Subject: Bugs and features
Date: Wed, 01 Nov 89 16:44:25 EST


Basically, everything looks good.  I'm going to be playing with 
Argus for the next few days, and will try to update the documentation
a bit.  I found a few things that were disconcerting...

Wendy


1.  When I bring up the ruleeditor for the first time, the "Add" and 
"Delete" menu options are grayed out.  Why?

2.  Message type:  I changed the type to "MSG", saved it, and then 
edited it.  When I bring the ruleeditor back up again, it displays
<undefined> in the message type window.

3.  Message type:  If I change the message type above, it simply adds
a new field below, rather than changing an existing one.  It should 
check if one exists.

4.  "Rule name" and "Message type" are different fonts.  Is this to 
make them the same length?

5.  The top bar is missing, when the message type field is added.
(There's space for it -- but it doesn't show up.)  Oh, I just used the 
TAB key and it outlines it...  Perhaps this is an interaction effect
with my Xresources.

6.  Message type:  in complex mode, the only possibility should be 
"exactly matches".  "Is less than MSG" doesn't make sense.  Also, I 
seem to recall that it was important that it match case exactly -- 
if this is still true, then we shouldn't give people the option of 
changing it to something other than "case sensitive text".

7.  Simple: I changed everything to COMPLEX, then changed it back to
SIMPLE.  I had independently changed one field to COMPLEX and then
changed it back as well.  The line separating the TO: from the rest of
the field was in a different place than on the other fields.