> It's me again.
> > If I specify the new Bitmap's format as pf32bit, the colors
> > are changed (from pf24bit).
> Yes. It's something I ran into yesterday afternoon. Testing proved that
> the bit orders are:
> pf24bit -> BB GG RR
> pf32bit -> 00 RR GG BB
Bitmap format spec I have.
From your other posts, it seems like you could use a copy of it.
E-Mail me if you are interested and I'll send it to you.
However, I do have a question. Perhaps I am a moron, but there
seems to be a fundamental disconnect between the name "32 bit"
and my arithmetic.
Note that the pf32bit format uses only 24 bits, JUST LIKE pf24bit.
The extra 8 bits are unused. Shouldn't the name "32 bit color" be
"24 bit color, but with a different byte order and 2 wasted bytes"?
I mean if you use 32 bits to carry only 24 bits of information, it
seems dishonest to call it "32 bit color" when it is no better than
"24 bit color".
What am I missing here?
You know, the same question goes for "16 bit color". It only uses
15 bits (3 bits for each red, blue, and green). The most significant
bit is unused. Shouldn't it be renamed:
"15 bit color with 1 wasted bit"?
Suppose I were to build a race car with a V-6 engine. I could put
a V-6 sticker on the fender and be honest.
But, then my competitor builds a car with an engine that has 8
cylinders. He only puts pistons, spark plugs, and fuel injectors
in 6 and leaves the last 2 as just empty weight in the engine
compartment. Well, he goes and slaps a V-8 sticker on the side
of his car. Everyone is going to go buy his car, because we all
know more cylinders = more power. Really, though, his engine
only has the same power as mine, but his car is carrying around
a bunch of dead weight. My car is actually better than his!
Shouldn't the same rules apply to naming color format?
Or maybe there is something going on that I don't understand!
At least the 4 and 8 bit color types are honest (if not confusing
by using a palette). 24 bit and monochrome are the only color
schemes that make sense.
The views in this post are entirely my own and do not reflect the
position of the U.S. Air Force