Besides adding a keep-alive for packet connections (that was Wish List Item 6) consider the following:
1) Do not issue the "Keep Alive Message Sent" line. This doubles the amount of space taken up by keep-alives which are already too cluttering. 2) Issue the keep alive message (CarriageReturn-LineFeed) only when it is needed, i.e. only after keep-alive time has passed since the last input line from the cluster. If DX spots are more frequent than the keep alive-time, no keep alive-need be issued. 3) If you wish to be very advanced...then write the incoming prompt (in response to the keep-alive transmission) on top of the previous prompt, thus reducing the clutter to an absolute minimum while still providing an indication it is running...which can be seen from the fresh time/date stamp in the cluster prompt. Ron Stordahl N5IN
