Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!ucsd!ucbvax!agate!tornado.Berkeley.EDU!vincelee
From: vincelee@tornado.Berkeley.EDU (Vincent H. Lee)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Screens flipping to non-interlace for no good reason
Message-ID: <1990May2.214814.18615@agate.berkeley.edu>
Date: 2 May 90 21:48:14 GMT
References: <5651@sugar.hackercorp.com> <15911@phoenix.Princeton.EDU>
Sender: usenet@agate.berkeley.edu (USENET Administrator;;;;ZU44)
Reply-To: vincelee@tornado.Berkeley.EDU (Vincent H. Lee)
Organization: ucb
Lines: 22

In article <15911@phoenix.Princeton.EDU> pfalstad@phoenix.Princeton.EDU (Paul John Falstad) writes:
>In article <5651@sugar.hackercorp.com> karl@sugar.hackercorp.com (Karl Lehenbauer) writes:
>>The problem is, sometimes an interlaced screen that's already loaded will,
>>when a ScreenToFront is done on that screen, come up as non-interlaced and
>>only show half the picture in the normal screen area.
>>
>>I thought it was my code for sure until it happened to the workbench screen
>>(I normally run with an interlace workbench).  A crash quickly follows.

Finally!!! I've been griping about this bug for about 3 years!!!!!  

It seems some intuition View structures or other get corrupted during depth-
changing which causes the delacing/crash.  A program which runs in the 
background repairing the structures was written by someone some months ago.

I used to crash my maching daily because my wb and editor were interlaced and
I was writing a program which openned a non-interlaced screen.  Since the fix...
no crashes!!!

If you mail me, I can mail you a uuencoded copy if you want...

-vince