> What are the differences between the bitmap version numbers
Some additions and changes to what you wrote, from looking at the PalmOS 3.1 (Window.h
and WindowNew.h) and PalmOS 3.5 (Bitmap.h) headers:
Compression - it appears that some compression has been around
(BitmapType.flags.compressed) since version 0 (Window.h). I don't know if it has
worked or not, haven't played with it.
Bitmap Chaining - there doesn't seem to be official support in the version 0
BitmapType (Window.h) for bitmap chaining - the "nextDepthOffset" field appeared in
the version 1 BitmapType (WindowNew.h).
Indirect Bits - indirect bits seems to be a version 2 (Bitmap.h) innovation.
> What do you have to do to insure that a bitmap will draw on a device
These are the steps I take to find out. They work (so far) in my environment, where
pixelSize is the number of bits per pixel...
- PixelSize == 8 means PalmOS 3.5 only.
- Version 2 bitmaps only display in PalmOS 3.5 - this is probably not always true,
especially for very simple bitmaps, but it sounds like a good rule
- Everything else is a comparison of BitmapType.pixelSize to your machine's
maxPixelSize. For the comparison, maxPixelSize would be determined by checking the
processor and OS. For example, a Palm III running PalmOS 3.5 will still only support
bitmaps with a pixelSize of 2 (or less).
I think that is right. It's how I do it. Not pretty, but effective so far. I'd love
to have a better way to do it...
--------------------------------------------------
David Tribble, INRI Hawaii
(808) 625 2118 (v) (808) 625 6315 (f)
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
