Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!rutgers!njin!princeton!phoenix!pfalstad
From: pfalstad@phoenix.Princeton.EDU (Paul John Falstad)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Screens flipping to non-interlace for no good reason
Message-ID: <15911@phoenix.Princeton.EDU>
Date: 2 May 90 15:59:18 GMT
References: <5651@sugar.hackercorp.com>
Reply-To: pfalstad@phoenix.Princeton.EDU (Paul John Falstad)
Organization: Princeton University, NJ
Lines: 21

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.

I've had the same problem.  I have an interlaced workbench as well, and
I have a program that opens a 320x180x5 screen in back of WB
(TopEdge = 20) and brings it to front when it's finished initializing
it.  Almost every time, though, when it brings it to front, the
workbench screen (20 lines of it) just above it changes to
NON-interlaced -- that is, it displays every other scan line.  A crash
usually follows.  Bug in Intuition perhaps??

-- 
Paul Falstad      INTERNET: pfalstad@phoenix.princeton.edu
PLink: HYPNOS     GEnie: P.FALSTAD  CIS:70016,1355
Disclaimer: Everything I said is false, including this sentence
"I'd like to leave the army, sir."  "Why is that?"  "It's DANGEROUS!"