Path: utzoo!utgpu!water!watmath!clyde!att!mtunx!rutgers!cmcl2!nrl-cmf!ames!decwrl!sun!pepper!cmcmanis
From: cmcmanis%pepper@Sun.COM (Chuck McManis)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Custom Bit Maps & Intuition
Message-ID: <55567@sun.uucp>
Date: 7 Jun 88 16:47:56 GMT
References: <10628@agate.BERKELEY.EDU>
Sender: news@sun.uucp
Reply-To: cmcmanis@sun.UUCP (Chuck McManis)
Organization: Sun Microsystems, Mountain View
Lines: 23

In article <10628@agate.BERKELEY.EDU> (Pete Goodeve) writes:
->
->This has probably all been dealt with before, but if so I missed it, and
->it has just become a sort of urgent problem...
		...
->I can, of course, open a window over the whole screen to put my bitmap in,
->but then the screen is going to get its own bitmap too at the moment it's
->created, which is a lot of wasted space if it's high-res/four-plane, say.
->Is there any way around all this, aside from going the non-Intuition custom
->viewport route?  I'll be grateful for any help.  Thanks,
->                                            -- Pete --

If you open a full size window that is the same size as the screen that
is SIMPLE_REFRESH, then the screen and window will share bitmap memory
and everything will be hunky dory. (plus you can write to it through 
either the screen rastport or the window rastport.) The only memory you
'waste' is for a rastport struct, some layers stuff, and a TextFont or
two. (less than 1K anyway). 


--Chuck McManis
uucp: {anywhere}!sun!cmcmanis   BIX: cmcmanis  ARPAnet: cmcmanis@sun.com
These opinions are my own and no one elses, but you knew that didn't you.