Steps to reproduce:

1. Upload this file
   
2. See that it only renders as

static const char PROGMEM font[] = {
    0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF,
    0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF,
    0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF,
    0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF,
    0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF,
    0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF,
    0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF,
    0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF,
    0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF,
    0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF,
    0xFF, 0xFF, 0xFF, 0xFF,
};

Other images work just fine.

Specifically, for the RAW mode. So that you can use a rotated image?

As far as I can tell, there is no reason an imported image can't be bigger than 256 pixels in one dimension since the image's ratio has no influence on the outputted bytes. The bytes simply correspond with 1x8 pixel sections that freely wrap around at the end of an image row to produce the one-dimensional byte array output.

Why this is relevant

I was trying to parse the bytes for an image of size 270x32, namely this one:

In this font, each character is 4 qmk-font-rows high and I arranged all the characters in one single row on the image so it's easier to find the matching sections of characters when displaying them (e.g. to display a 1 I write bytes 4 and 5 in the first OLED row, bytes 34 and 35 in the second and so on).

To use this tool as it is, it was necessary to rearrange the image like this

to avoid the hard 256 pixel limit on the width and still get the same arrangement for easy displaying. The same exact byte output can also be achieved by simply removing the code snippet that limits the image's dimensions and using the first image that would otherwise be too wide.

When editing font or raw, the byte array is updated immediately. However when editing logo, it doesn't seem to ever update the byte array. There are no errors thrown to the JS console.

Instead of having a set size based on the keyboard, it would be nice to have a number of options, or even a "custom" option. Eg:

• 128x32
• 128x64
• 64x32
• etc

This will allow a lot more customization of the OLED screen and the possibility of doing animations that are not full screen.

Namely, don't parse comments in files.