Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!watmath!clyde!caip!think!nike!lll-crg!lll-lcc!qantel!ptsfa!pttesac!vanam From: vanam@pttesac.UUCP (Marnix van Ammers) Newsgroups: net.micro.amiga Subject: Re: More VT100 Problems Message-ID: <305@pttesac.UUCP> Date: Tue, 14-Oct-86 11:41:58 EDT Article-I.D.: pttesac.305 Posted: Tue Oct 14 11:41:58 1986 Date-Received: Mon, 20-Oct-86 22:15:34 EDT References: <93500049@convex> Reply-To: vanam@pttesac.UUCP (-Root Admin-) Organization: Pacific Bell ESAC, San Francisco Lines: 42 In article <93500049@convex> danny@convex.UUCP writes: > >For the nth time, I'd like to congradulate everybody involved in the VT100 >program but there seems to be (another) bug. When VT100 (old or new) starts >up, I have it set to open it's own two-color screen. The window starts down >just a little. Everything is fine and the window is a perfect 640X200. > >BUT, after I move THE SCREEN, things change, the screen grows down a little >and the y hot point of the mouse goes down some. What's even weirder, when >I drag the screen down, the top of the pointer (original y hot point) is at >the point where the mixed up point is normally but the y point gets mixed up >again later. It's just plain weird. > >The window before and after moving the screen is 24 lines down but after the >screen is moved, the window can move down without cutting if off. This freaks >me out because the window shouldn't be able to move below the screen but it >does and after the screen is fixed, doesn't but can go down exactly one line. > >I hope somebody can understand what I've said because I'm a little confused >myself... Thanks. I think I have the same problem. It is so hard to describe that I haven't bothered to try. But moving the window/screen up and down causes problems. As for enhancements, I would like an auto-wrap option and also a printer on/off option. One more thing. I mentioned a while ago that *my* version ov VT100 leaves DTR on even after I click the go-away gadget. I thought this was a real neat feature. But according to Wecker, the program does *not* leave DTR on. So now I've found that this thing that I thought was a feature, actually only happens under certain circumstances. I'm trying to isolate just when I get this feature. For some reason I could not get the feature to work at all last night (DTR kept going off when I quit the program) but I swear, the night before it was working just as I've said: DTR remained on. I will post the details when I figure it all out. I want to join the Dave Wecker fan club too. Marnix