A palm OS tbmp resource is going to be a lot bigger than a jpeg because palm bitmaps are stored with either no or lossless compression. Jpegs are highly compressed. On the device/sim, bitmaps may look grainy if you do not set the screen mode to 16-bit. Set the screen to its highest depth with WinScreenMode.
> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:bounce-458778- > [EMAIL PROTECTED] On Behalf Of Brian > Sent: Thursday, September 08, 2005 2:48 PM > To: Palm Developer Forum > Subject: output resource size is greater than 64K size limit > > I'm using Codewarrior 8.3 and getting this message. I usually just > create/edit JPGs outside of CW, and then paste them into the Bitmap in the > Constructor. In this case, the bitmap that is supposedly exceeding the 64K > size limit was originally a JPG of only 8k, so how is this possible? > > This size issue happens when I set the Bitmap Depth to 16-bit. It compiles > fine with 8-bit, although it looks uglier. I thought JPEG was 24-bit, so > does it have something to do with converting it from 24-bit to 16-bit? > > One way I've tried getting around this was to break the image into > sections (the original lores image was 133x139 pixels). By doing this I > was able to use the 16-bit depth, but then I noticed another issue. The > images look fine in constructor, they look like they've retained the > detail and depth of the original JPG, but when running in the Simulator > (or an actual device, I checked there too), the image looks grainy. Any > idea why? > > Thanks > -- > For information on using the PalmSource Developer Forums, or to > unsubscribe, please see http://www.palmos.com/dev/support/forums/ -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
