On Mon, Sep 25, 2000 at 10:21:37AM -0700, David Fedor wrote:
> >So, two supplemental questions:
> >1) why does the PalmOS sample code use 1/2/8-bit icon/bitmaps but not
> > 4-bit ? Because no device has a 4-bit display ?
>
> Well, nothing really uses 4-bit right now, though the Palm IIIc devices can
> certainly run in that mode if an app switches it to them. And if you're in
> 4-bit mode the system will use the 2-bit family member, which is usually
> what you'd want anyway. So we saved rom space and skipped that depth for
> now.
I wish you saved rom space by making some of the default apps optional
instead :).
Since I am doing imaging I do use 4 bit. So do most other imaging
programs that run on something other than the IIIc.
> >2) What Palm device has a 2-bit display ?
>
> Every device ever shipped so far actually can display in 2-bit mode, but
> the OS support for doing that only started in Palm OS 3.0. And out of the
> box, everything runs in 1-bit mode except for the Palm IIIc (which defaults
> to 8 bits) and Web Clipping always switches the system to 2-bit mode.
> Other than those two exceptions, everything I know of just uses the default
> depth, so usually you're in 1-bit mode.
To add one detail, you need PalmOS 3.3 or greater for the set display
mode calls to set 4 bit mode. So OS 3.1 devices (e.g. Handspring
Visors) can display 4 bit, but you can't do it with PalmOS calls.
This creates lots of fun code trying to display a 4bpp image on every
PalmOS device in the highest possible depth.
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
