home *** CD-ROM | disk | FTP | other *** search
- Path: aargh.incubus.sub.org!marc
- From: marc@aargh.incubus.sub.org (Marc 'Nepomuk' Heuler)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: Demo/game to OS friendly part II
- Message-ID: <QkW2y*Roa@aargh.incubus.sub.org>
- Date: Tue, 06 Feb 1996 23:28:52 CET
- Reply-To: marc@aargh.incubus.sub.org
- References: <4dg16j$ha1@serpens.rhein.de> <4djdn2$2tk@sunsystem5.informatik.tu-muenchen.de>
- <gBe1y*tna@aargh.incubus.sub.org> <4f4kru$hj6@oreig.uji.es>
- Organization: Data Design
- X-Newsreader: Arn V1.03a
-
- In article <4f4kru$hj6@oreig.uji.es>, Jorge Acereda Macia writes:
-
- > I can't find info in the manuals referring to allocating non-interleaved
- > contiguous bitmaps in chip mem.
- > Should I allocate it as BMF_INTERLEAVED|BMF_DISPLAYABLE and change the
- > interleaved flag in the bitmap structure?
- > Should I allocate width*height*planes+8 bytes in chip mem to ensure
- > alignment and create the bitmap structure myself?
-
- If you don't need an interleaved bitmap, then don't ask for one (ie do not
- set BMF_INTERLEAVED). If you need your bitmap to be non-interleaved, then
- grab the planes via AllocRaster(), and merge them to a valid bitmap using
- InitBitmap(). Note well the difference between those two requirements.
-