[79] in Zephyr_Comments
re: zwgc killing pings?
daemon@ATHENA.MIT.EDU (Mark W. Eichin)
Mon Aug 8 10:44:00 1988
Date: Mon, 8 Aug 88 10:43:36 EDT
From: Mark W. Eichin <eichin@ATHENA.MIT.EDU>
To: John T Kohl <jtkohl@ATHENA.MIT.EDU>, Dan Schmidt <dschmidt@ATHENA.MIT.EDU>
Cc: zephyr-comments@ATHENA.MIT.EDU
In-Reply-To: John T Kohl's message of Fri, 5 Aug 88 13:30:56 EDT <8808051730.AA07713@LYCUS.MIT.EDU>
Something that would be _really_ cool but perhaps hard to implement would be
if when a zephyrgram came up, it automatically killed off the ping message
associated with it. Ping messages are very useful so you can see who's in
the middle of zwriting you, but it's a pain to kill off every zephyrgram
twice (once for the message and once for the ping). If this were implemented,
the ping messages up on the screen would serve as a record of who has started
to zwrite you, but hasn't finished yet. It would also cut in half the number
of times that I have to send the cursor up into the corner of the screen to
kill a message.
Actually, it is simple.
The sources to zbrowser contain all of the code needed to `catch'
incoming messages, read the summary line off of them, and delete them.
Your mission (should you chose to accept it) is to put this all
together in the right order. If you put a special "does opcode/match
ping/summary PING: normal summary/endmatch/enddoes" type expression in
your windowgram file, then you just strncmp("PING:", str, 5) the
summary line, if it is true then save the summary and window-id
somewhere, if not scan the table for a "PING: "str and if you find it,
delete it (send it the right button press event.)
Let us know when you have it implemented...
Mark Eichin
<eichin@athena.mit.edu>
Project Athena ``Watchmaker'', ZephyrTeam
