Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!mit-eddie!ll-xn!ames!amdahl!acs
From: acs@amdahl.amdahl.com (Tony Sumrall)
Newsgroups: comp.sys.amiga
Subject: Re: Vt100 bug: Squished, and more
Message-ID: <18066@amdahl.amdahl.com>
Date: Tue, 10-Nov-87 22:35:32 EST
Article-I.D.: amdahl.18066
Posted: Tue Nov 10 22:35:32 1987
Date-Received: Fri, 13-Nov-87 05:19:03 EST
References: <1811@tekred.TEK.COM>
Reply-To: acs@amdahl.amdahl.com (Tony Sumrall)
Distribution: na
Organization: Amdahl Corporation, Sunnyvale CA
Lines: 48

In article <1811@tekred.TEK.COM> joels@tekred.TEK.COM (Joel Swank) writes:
>From VT100 V2.7 readme:
>
>	- Nagging bug: On 2nd and subsequent uses of the requester, the
>	  1st character of the last use is redisplayed.  Intuition bug?
>
>I got tired of this sucker last weekend, so I tracked it down and 
>squished it.
>
>The Answer:

Thanks, Joel!  I'll include that in R2.8 (due, maybe, end of year).

>Another irritation with this program:
>
>- req() subroutine in window.c leaves keyboard active in requestor 
>  window.  It should re-activate main window.

Well, your "fix" will do but...how do you know that you should re-activate
the main window?  The requester could've been pulled up because of a
transfer requested via a script file.  It would be possible to find the
last active window prior to the Activate call but how do you know that
that's the window that should be reactivated?  Unless someone can convince
me that there is a sure-fire way to *know* which window needs to be
reactivated I'm not planning on incorporating this into the newest rel.

>There's another addition I needed, so I put it in while I was in there:
>
>In order to have a beep at completion of kermit file transfer.

I'll include a new flag that can be set for compilation as well as
toggled by script/init cmd.

>Joel Swank

If anyone else has fixes or requests, send 'em to me.  Like I said, I
plan on releasing 2.8 sometime around the end of the year.  I'll post a
list of the things that I've already got planned in the near future (yes,
I'm supporting overscan (the right way!), I'll fix the AbortIO(), the
filelocking (aka currentdir bug) and the overzealous xmodem chopping).
I'm definitely including kermit support for long packets and may even
redo the xmodem stuff to include Y/Zmodem support (anyone wanna volunteer
to send me new x/y/zmodem code? :-)
-- 
Tony Sumrall acs@amdahl.com <=> amdahl!acs

[ Opinions expressed herein are the author's and should not be construed
  to reflect the views of Amdahl Corp. ]