Regarding the latest pilrc 2.9p5... Been going through the paces with high-density bitmaps, but after exchanging emails with some folks at Palm I don't understand some limitations regarding double-density bitmaps created with the latest pilrc2.9.
Why must the "DENSITY 2" flag only apply to members of a "family"? Why not just add a density flag to any BITMAP or BITMAPCOLOR or anything else? Why can you "not have only bmp with DENSITY 2 in BitmapFamilyEx."? (As far as I can tell, this isn't a limitation inherent in new bitmaps. Why couldn't you have a resource that was ONLY a double-density bitmap?) While it often makes perfect sense to have a family, where the OS will simply choose the correct high-density bitmap, I find in practice that the 64K limit to the total "family" size often keeps this from being practical. In which case, you'll have to add the high-density version to a separate resource, and in the current form, you'll thus need a "dummy" density 1 bitmap to fulfill the current requirement. I see this as a limitation. It might simply be an early pass at revising pilrc, but I for one could really use the ability to make a double-density resource as a standalone. Comments/rebuttal welcome. Thanks, zane ----- r. zane rutledge - http://www.rzanerutledge.com/palm/ -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
