Bitmap Table Confusion

[1BitGodot (Phillip Madden)]

I’m not sure this is even a bug, but the way it is done in the C-API can lead to confusion or I’m not doing it correctly. The following is a set of images that I used to produce the bitmap table, notice that the frames start from 1-8.

However, when I use the getTableBitmap API function to retrieve each frame, I will have to start from 0 to access the correct bitmap image; this means that the frame number has to be 0-7.

SetBitmap(gfx->getTableBitmap(tiles, angle));

So this is the confusing part: the images have to start from index 1. If I start from index 0, it creates another extra bitmap table. The even funnier thing is the extra bitmap table is created from the last image and not even the first one. But to fetch the right image, I have to start from index 0. Why not just use one standard? Either both start from 0 or both start from 1?

Plus, there was no answer to this Bitmap table question, and the documentation for LUA says to use index 1 to access the 1st frame. This kind of issues and inconsistency is why using Bitmap tables can be confusing.

Creating New Bitmap Tables

Hi, Using the C SDK, I’m trying to create a bitmap table on the fly with the following code: // Create a new table bitmap with 4 16x16 cells LCDBitmapTable* tableBitmap = pd->graphics->newBitmapTable(4, 16, 16); // Get the first bitmap from the new table and get its data int w, h; LCDBitmap* singleBitmap = pd->graphics->getTableBitmap(tableBitmap, 0); pd->graphics->getBitmapData(singleBitmap, &w, &h, 0, 0, 0); The table is successfully created, but when I check the width and height of the fi…

[DraperDanMan]

Bitmap tables aren’t stored in that format as the documentation says here: Inside Playdate
Then all your code will work as expected. Example of a bitmap table png:

EDIT: Actually you’re right! they do say they support sequences. I guess it’s a little weird. Sorry about that!