Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!uunet!smosjc!brett
From: brett@smosjc.UUCP (Brett Coon)
Newsgroups: comp.sys.amiga.tech
Subject: Who frees CUSTOMBITMAPs?
Keywords: OpenScreen, CloseScreen
Message-ID: <324@smosjc.UUCP>
Date: 7 Jan 91 22:53:13 GMT
Organization: S-MOS Systems, San Jose, Ca., USA
Lines: 24

When you open a screen with the CUSTOMBITMAP flag set in the NewScreen struc-
ture, will CloseScreen free the bitmap memory?  If so, how can I prevent this
from happenning so that I can free the memory myself at a later time?

On a related topic, is it correct that memory must be freed in the same block
sizes in which it is allocated?  I.E. if I use AllocRaster to allocate a 
640x200 bitmap, I can't free it as two 320x200 bitmaps, right?

Finally, if I want to open a 320x200 pixel screen that shows 1/2 of a 640x200
pixel bitmap, is it correct that I should specify 320x200 in the NewScreen
structure but 640x200 in my (custom) BitMap structure?  I tried specifying
640x200 in both (but not setting the HIRES flag in NewScreen), and it appears
to have opened an overscan screen, which is not what I want.  I'd prefer not
to play with the RasInfo and related structures any more than I have to, so
I'm looking for a combination of settings that will open the appropriate
screen directly.

Thanks,
-brett

-- 
|Brett Coon           |  uunet!smosjc!brett                       |
|S-MOS Systems, Inc.  |  "Very exciting... as a luggage problem." |
|San Jose, CA         |            -Joe Vs. The Volcano           |