BmpGetNextBitmapAnyDensity doesn't seem to do the right thing on bitmap families that have high-density but no low-density members (i.e., when the first bitmap in the family is the dummy bitmap).
In these cases, BmpGetNextBitmapAnyDensity(bitmapP) returns bitmapP, which doesn't seem useful and isn't the behavior I'd expect. Moreover, I'm not sure what the right way is to skip over the dummy bitmap. Right now if BmpGetNextBitmapAnyDensity(bitmapP) == bitmapP, I assume bitmapP points to a dummy bitmap header and increment bitmapP by sizeof (BitmapTypeV1) bytes. I figure it's fairly safe, since I can't imagine the dummy bitmap structure changing, but it still makes me a bit uncomfortable. Also, on a sort of related topic: Is there any way to retrieve the same bitmap family member that WinDrawBitmap would choose for the density and bit-depth of the current draw window? If there's not, shouldn't there be? Some of the Bmp* functions retrieve values from the first bitmap in a family instead of the best-suited one for the draw window, which usually is not what I want. Currently I iterate through the bitmap members myself, trying to reproduce the WinDrawBitmap logic (which is how I ran into the problem above). I'm aware of the BmpRsrcBestMemberFromFamily function from the BitmapRsrc sample code, which certainly is better than nothing, but it's not guaranteed to produce the same behavior as the OS... __________________________________________________ Do you Yahoo!? Yahoo! Web Hosting - Let the expert host your site http://webhosting.yahoo.com -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
