Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!rutgers!nike!ucbcad!ucbvax!CORY.BERKELEY.EDU!dillon
From: dillon@CORY.BERKELEY.EDU (Matt Dillon)
Newsgroups: net.micro.amiga
Subject: Re: Making a screen invisible ( rephrased )
Message-ID: <8610270357.AA05057@cory.Berkeley.EDU>
Date: Sun, 26-Oct-86 22:57:48 EST
Article-I.D.: cory.8610270357.AA05057
Posted: Sun Oct 26 22:57:48 1986
Date-Received: Mon, 27-Oct-86 05:32:45 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: University of California at Berkeley
Lines: 22


>No, that really isn't what I was interested in. I guess that I probably
>didn't express what I needed well enough. What I want is to be able to
>do rendering to an INTERLACED screen in memory, with as little ( ideally
>none ) effect on the display as possible. I don't like an interlaced
>workbench, and this program could run for quite a few hours ( days even ).
>What I had in mind, and I guess that I am dreaming is something such as :

	<sigh>  All you need do graphics rendering is a rastport... you don't
need to open any screens or anything like that... just setup the
fields properly in the rastport, allocate a bitmap (read carefully RKM V1
on graphics... If I remember right, rastports for interlace screens are
slightly different).  All bitmap memory must, of course, be CHIP.  When
you are through rendering it shouldn't be too difficult to open an interlace
display and simply transfer the info... in fact, I think you can even
specify you have a custom bitmap and use the same bitmap you used for
the original rendering.

	I've never specifically tried doing this myself.  Good Luck.

	
					-Matt