I'm pretty sure that I'm the only one who finds Constructor's UI to be
unnecessarily arcane ;-), but here is my experience on some points about
using bitmap families:
- When you set the bitmap size in the family spec panel, all your
bitmaps must be of that size. However, you must set each bitmap's size
individually when you edit it. It took me a while to find out how to do this
-- it's on the Options menu while you have the bitmap open for edit.
- Family members must be assigned in ascending bit-depth order. You
don't need one for each depth, as the OS will select the one that is <= the
device depth.
- The ID of the bitmap family must be unique with respect to the IDs
of all individual bitmaps. This is not obvious when using Constructor, but
the app will fail to load into POSE if there is a duplicate resource ID.
Having learned these details, I was able to successfully create a bitmap
family for a command bar button that now looks really good on a color Palm
and also displays in b&w on one of those old, dark-ages monochrome devices.
BTW, does anyone else find it irritating that Constructor does not save the
path to the most recently opened project like every other known Windows app
does? Every time I start it up, I have to browse down my directory tree to
get to the same resource file for my project. This seems like a really
simple feature to include. After all, the IDE supports it!
Doug Gordon
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
