how about using the pilrc plugin ONLY for your bitmap? :) the official syntax: BITMAP... {normal options here} BITMAPPALETTE "file.pal" PALETTE ID {id} "file.pal"
I tried this approach yesterday and couldn't get it to work whatever I did.
On the way, I stumbled over a PilRC bug. The palette-parsing (ParsePaletteFile()) doesn't handle newlines directly after the blue value (case 2:). I checked the patches but couldn't find any correction.
This also makes me wonder if anybody really have gotten this to work. Even if I patch the code (or add spaces after each blue value) and get a nice palette resource, I still can't get it to work. The simulator complains about "shadow bitmaps" and other things I've never heard of.
Thanks for the report... I just looked at that code, and I rewrote the function to just use fscanf and not fool with memory buffering and trying to parse numbers itself. It makes the code a lot simpler, and it makes it more robust versus whitespace handling. I'll test this out, and include it in the next Metrowerks source drop of PilRC that I send to Aaron.
BTW, shadow structures are used by PACE -- internally, PACE converts 68K structures to an ARM-native format, then maintains shadow versions that are in 68K format that are visible to routines. Not all structures are shadowed, only those likely to be changed by user code. I'm not sure what's happening with palette and PACE -- it's not something I've had to handle yet.
--
Ben Combee <[EMAIL PROTECTED]>
CodeWarrior for Palm OS technical lead
Palm OS programming help @ www.palmoswerks.com
-- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
