Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!lll-crg!ames!ucbcad!ucbvax!cbatt!neoucom!wtm
From: wtm@neoucom.UUCP (Bill Mayhew)
Newsgroups: comp.sys.amiga
Subject: Re: DBW vt100 v2.3 running on custom sc
Message-ID: <337@neoucom.UUCP>
Date: Sun, 14-Dec-86 00:00:56 EST
Article-I.D.: neoucom.337
Posted: Sun Dec 14 00:00:56 1986
Date-Received: Tue, 16-Dec-86 01:19:29 EST
References: <334@neoucom.UUCP> <172200014@uiucuxc>
Organization: Northeastern Ohio Universities College of Medicine
Lines: 28
Summary: vt100 v2.3, Dillon/Drew shell v2.01a, wb1.1 v31.334


Hi;

See the summary above for the software mix that I was running when
I had the problem.  The difficulty crops up when you're running
vt100 on a custom screen instead of the wb screen.

The thing that set off the goofed up display is moving the window
that vt100 is running in down so that you can get at the depth
arranger gadget on the custom screen's drag bar.

I don't really think that Intution is getting mixed up about the
mouse's hot spot, although it rather looks like that.  I think that
something in the rastport data sturcture for the custom screen is
either clobbered or missing.  If you can manage to get the wb
screen to the front, usually dragging one of its windows will
usually cause things to snap back into position.

If you use closed-amiga-n and closed-amiga-m to rearrange the
screens, you'll be o.k., and not see the above bug.

Sorry that I haven't been unlazy enough yet to pick through the
source for vt100 yet to find the place where this happens...

This seems to be a pretty nonfatal bug, so I wouldn't loose too
much sleep over it.

  --Bill