hamilton@uiucuxc.cso.uiuc.edu (12/11/86)
>>>else pressing leftamiga-N results in a rather peculiar looking >>>display, although the machine doesn't crash. If you can manage to > >>Yep, I've got the same bug here. I mentioned it a few months ago > >Damn. Right after posting that I had the same bug with VT100 2.3 >screens, I tried to duplicate the problem and couldn't. I could >swear that I had the problem with VT100 2.3 before. Maybe I wasn't >on WB 1.2 which I am now. which KS/WB were you using? a friend of mine had a similar very bizarre problem, but only when using 1.2B4 or 1.2B6 (i think). wayne hamilton U of Il and US Army Corps of Engineers CERL UUCP: {ihnp4,pur-ee,convex}!uiucdcs!uiucuxc!hamilton ARPA: hamilton%uiucuxc@a.cs.uiuc.edu USMail: Box 476, Urbana, IL 61801 CSNET: hamilton%uiucuxc@uiuc.csnet Phone: (217)333-8703 CIS: [73047,544] PLink: w hamilton
wtm@neoucom.UUCP (Bill Mayhew) (12/14/86)
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