Can't invert colors or fg/bg when using bitmaps

[raykamp-tht]

I'm designing fonts for an OLED display that has inverted colors. I'm designing pre-rasterized "bitmap strikes" to look good on a low pixel density display. Using the following change in the Appearance Editor, I'm able to get some of the functionality I need. Presumably others use FontForge to design for devices with grayscale or monochrome OLEDs have inverted colors.

It works very well in the "Metrics Window" when viewing with a bitmap strike.

However, no matter what color settings I select in the Appearance Editor, I'm unable to change the bitmap foreground color in the main window and also the bitmap window. Because of that, I'm unable to have an effective workflow where I'm going between testing fonts in Metric Window and editing bitmap glyphs:

Here is the main window. The bitmap glyph foreground is black and can only be seen when highlighted.

It's worth noting that this isn't a problem when viewing vector outlines of the font:

It gets extra strange in the Bitmap Window. It appears that despite changes to the bitmap foreground and global background colors in the appearance editor, The "shades" palette colors do not change. I would expect/hope that those shade value would linearly distribute between the background and foreground colors, as they appear to be doing when rendering in the Metrics Window.

Here's the version of the software being used:
Windows 11 Pro 10.0.22631 Build 22631
Font Forge version 20230101

Does anyone know how I can get the bitmap editor window to invert its shades? (same goes for the main window, but that's less important)

When reporting a bug/issue:

• Screenshot
• The FontForge version and the operating system you're using
• The behavior you expect to see, and the actual behavior
• Steps to reproduce the behavior
• (optional) Possible solution/fix/workaround

When you open an issue for a change/improvement/feature request:

• A description of the problem you're trying to solve, including why you think this is a problem
• If the feature changes current behavior, reasons why your solution is better
• (optional) Possible solution/fix/workaround