My understanding is that neither WinScreenLock or WinScreenUnlock ever
copies any of the bits when winLockDontCare is passed in. However, it does
allocate an offscreen window if the device doesn't support special VRAM to
allow the screen hardware to point to two different areas of memory. I have
no idea which devices support special VRAM, but I have a feeling from the
numbers you're getting that you're testing on a device without special VRAM.
Note that because of this issue, you really don't know what will be on the
screen you're drawing to after calling WinScreenLock(winLockDontCare). If
the hardware supports special VRAM, you'll get the second area of VRAM in
whatever state you last left it in. You can keep track of this state and
deal with updating it (a lock-step arrangement where each area of VRAM is
used for half the frames). However, if the hardware doesn't support special
VRAM, you'll get a chunk of dynamic memory that was just allocated for you,
so you have no idea what state that memory is in. When you say you don't
care, I guess you really have to mean it!
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
