unsigned short clr_555_to_fmt[32768];
unsigned short clr_fmt_to_555[65536];

All colors would pass through the first array before displaying them, and if you need to read information back, pass them through the 2nd.

The reason they are different sizes is the first only takes a 555 amount, and the second possibly uses 565.

If this doesn't make much sense, let me know and I'll type something better -- I'm at work right now.

Now, about using malloc and static arrays:
it doesn't really matter. It's just coding style. It some cases though, using a static array will bloat the .exe file.

As for using int and such, you have to remember that int is not a fixed size - it will vary from machine to machine and depending on the compiler.

Use short for 16 bit, and long for 32 bit
(on a x86 machine at least).

Jim

Here's what I do: All my tiles are stored in a 555 format, just because I definately know that's what it is. All color calculations performed are 555 no matter what.

When it comes time, say to load a tile into the cache, it will pass through a conversion function to convert to the screen format.

So, let's say we have a 32x32 tile stored at 555 format and this is my loading function:

for(i=0;i<32;i++) {
fread(&buf, 1, 32*2, fp);
for(j=0;j<32;j++)
buf[j] = clr_555_to_fmt[buf[j]];
buf += page.lpitch;
}

I never have to worry what the screen format is. Let's assume I'm reading a pixel from a screen buffer or tile buffer or whatever to work on:

color = page.ptr[12];
color555 = clr_fmt_to_555;<BR> <BR>Then I do color conversions based on 555 format to color555 variable, then I can write it back:<P> page.ptr[12] = clr_555_to_fmt[color555];<P><BR>Now, to setup the conversion tables, just do this:<P>unsigned short clr_555_to_fmt[32768];<BR>unsigned short clr_fmt_to_555[65536];<P>for(i=0;i<65536;i++) {<BR> // convert 555 to format<BR> if(i < 32768) {<BR> red = (i >> 10) & 31;<BR> green = (i >> 5) & 31;<BR> blue = i & 31;<BR> clr_555_to_fmt = (red << 11) | (green << 5) | blue;<BR> }<P> // convert format to 555 - assume 565<BR> red = (i >> 11) & 31;<BR> green = (i >> 5) & 31;<BR> blue = i & 31;<BR> clr_fmt_to_555 = (red << 10) | (green << 5) | blue;<BR>}<P>Please excuse me if this is a little off - I'm trying to do this from memory, but it looks right. You should get the idea.<P>Just create a better one that shifts and arranges the colors based on the info you get from GetSurfDesc.<P><BR>Thanks about TLB. It's being totally revamped - we have a new graphics and sound engine, plus some awesome stuff going in - we hope to have a new demo in the next couple of months.<P><BR>Jim Adams<P>

CU,
Alex

------------------
Alexander Stockinger
Programmer

As far as porting, you can alway generalize function calls and use DX in those. When you port, simply change a couple routines and it's done.

Jim