Guilherme C. Hazan wrote: > >AFIK, the Z22 (no Zire 22) can draw true 16bpp. The last PalmOne device > >non 16bpp as I know is old Palm IIIc. > > A program i have works fine on Treo 600 but displays absolutely nothing on > the 22. And both have a 160x160x16bpp screen.
I have seen a similar thing happen: my application worked fine on the LifeDrive and the simulators for other devices, when run in 16bpp display mode. But, when I loaded the app into my Tungsten E, the icon didn't appear in Launcher. I thought something went wrong with the Hotsync, but the database showed up when I looked for it with Filez or ZLauncher. (And although I'm not sure, I think I remember having a similar problem with button bitmaps in my forms.) The fix was weird, and I don't understand why it worked: I deleted the 256-color (8bpp) application icons. After that, no problem! Apparently, when the E didn't see the 256 color icon bitmaps, it then was forced to use the 16bpp icons, and dither them. The bitmaps don't look as nice on the Tungsten E, but at least they show up! As far as I'm aware, the Tungsten E is "supposed" to display 16 bit images(??), but I think there are differences in capabilities of the display hardware, and the way it is supported, between the higher end models (e.g., LifeDrive, and maybe your Treo 600), and lower end models (such as the Zires, Z22, and Tungsten E). This is just a theory, and I'd love to hear from someone at Palm (Ben?) who can verify or discount it. And am I doing something wrong? It seems really strange that I can fix a problem by deleting 8-bit images from my bitmap families! Jay Ts -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
