Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!zardoz.cpd.com!dhw68k!emmayche
From: emmayche@dhw68k.cts.com (Mark Hartman)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Off Screen Bit Maps
Message-ID: <1990Dec19.231852.25331@dhw68k.cts.com>
Date: 19 Dec 90 23:18:52 GMT
References: <1990Dec17.212129.27971@morrow.stanford.edu>
Organization: Wolfskill & Dowling residence; Anaheim, CA (USA)
Lines: 14

In article <1990Dec17.212129.27971@morrow.stanford.edu> craig@pangea.Stanford.EDU (Craig Jarchow) writes:
>Question: How can one use offscreen bit maps that appear and disappear during
>a program and avoid heap fragmentation? I notice that 
>offScreen.portBits.baseAddr must be a pointer, not a handle. Should I allocate
>a handle anyway, and lock and dereference it when I need to draw on the
>bit map or CopyBits() from it?

Precisely.

-- 
Mark Hartman, N6BMO           "What are you just standing there for?  Where
Applelink: N1083 or BINARY.TREE      do you think you are, DIS-ney World??"
Internet: emmayche@dhw68k.cts.com                -- General Knowledge, from
uucp: ...{spsd,zardoz,felix}!dhw68k!emmayche                CRANIUM COMMAND