Ben, Thanks for the reply! I think I understand what your getting at. However, I don't know how to separately dump the bitmap header and bits. I thought it was just a simple task of doing the following DmWrite call:
rc.Write(nOffSet, (BitmapPtr)sig->m_bmpPtr, nLen3); The Bitmap is created by the following call: m_bmpPtr = ::BmpCreate(m_rect.extent.x, m_rect.extent.y, nDepth, NULL, &err); Why would this code work on a 4.1 OS Palm but not on a 5 OS Palm? Also, how do I separate the bitmap header and bits. Thanks again for your help!! David ----- Original Message ----- From: "Ben Combee" <[EMAIL PROTECTED]> To: "Palm Developer Forum" <[EMAIL PROTECTED]> Sent: Tuesday, October 21, 2003 2:26 PM Subject: Re: Strange BitmapPtr Problem in Palm OS 5 > At 01:10 PM 10/21/2003, David R. wrote: > >Please help! > > > >For some reason, after capturing a persons bitmap signature within a > >gadget > >to a BitmapPtr and after doing a DmWrite of the BitmapPtr the data that > >is > >stored is not a valid bitmap but instead a dump of the dynamic heap. The > >same code utilized on an earlier Palm OS works just fine. > > How are you getting the bitmap pointer? Have you considered that you > might > get an indirect pointer, and you need to separately dump the bitmap header > and bitmap bits into your record, possibly fixing the indirect flag? > > -- > Ben Combee <[EMAIL PROTECTED]> > CodeWarrior for Palm OS technical lead > Palm OS programming help @ www.palmoswerks.com > > > -- > For information on using the Palm Developer Forums, or to unsubscribe, > please see http://www.palmos.com/dev/support/forums/ > -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
