> In one of our apps, we do the following: > > Err error = 0; > WinHandle saveWinH = NULL; > BitmapType *bp; > > saveWinH = WinSaveBits(bounds, &error); > bp = WinGetBitmap(saveWinH); > > // Validate Image Offset... > imageSize = MemPtrSize(bp); > > > This works well, actually, on all 3.5/4.x devices and to-date have > experience no ill effects. However in OS/5 the Simulator blows up big time > at the MemPtrSize() function. If there's a better way to get the size of > the bitmap, I'm open to it.
this fails on OS/5 cause the manner in which the os allocates memory for bitmap resources has changed. the right api to use is BmpSize() and BmpBitsSize() for determining the size of the bitmap structure and an individual bitmap. there are also some new glue routines for bitmaps. > On a side note, has anyone published anything that discusses how programs > that scribble on the screen can capture the screen or portions from in > PalmOS 5 and what we'll need to do to make that compatible with earlier > versions? And backwards? I'd like to give my users the ability to use > sketches they've created in prior devices, but for now have to 'turn off' > that functionality. why should this be a problem? if your doing it right, you should be able to store the bits of your bitmap, and, reproduce them on any version of the OS (if you want grayscale, need to have 3.0) --- Aaron Ardiri [EMAIL PROTECTED] CEO - CTO +46 70 656 1143 Mobile Wizardry http://www.mobilewizardry.com/ -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
