Ah ha! The /-c/ (etc.) is used if the bitmap isn't in a family. For example, if I have a 2-bit (4 gray) bitmap and reference it directly, it'll show up as 1-bit (black and white) unless I begin the name with /-2/. However, if that image is in a family and is specified as 2-bits, then it'll show up in grays regardless of the name.
In my app, the graphics are either black and white, or are supplied in a family (with b&w, gray, and color). However, I had an occasion where the same gray image would be displayed on all platforms (3.0+). I had to use the /-2/ naming convention or put this single image in a family (putting it in a family cost 3k in prc file size). Steve Achelis (talking to himself, and in third-person no less) Steve Achelis <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > > I'm using Constructor 1.5b7. I see the docs say I should name my bitmaps > special if they are multi-bit. E.g., begin the resource name with /-c/ for > compression. However, I've tried with and without the /-c/ and the file > size is identical. If I set the compression to Run Length Encoding in the > bitmap family, the file is significantly smaller... Anyone know if the /-c/ > was for earlier versions. > > > > -- For information on using the ACCESS Developer Forums, or to unsubscribe, please see http://www.access-company.com/developers/forums/
