SiegeLord

In principle yes, but a lot of the complexity lies in the synchronization code, and once that's separated from the decoding code, the maintenance burden is reduced significantly. After that,...

The issue appears to be that `al_get_monitor_info` does not reflect the scaling factor, while `al_set_window_position` does. When DPI awareness is disabled, this means that `al_set_window_position` will be getting values that...

Actually, I am not so sure about OSX. The key question is whether toggling DPI awareness alters the values returned by `al_get_monitor_info`. If it does, then we should fix Windows.

I tried this on OSX, and in apps which declare themselves as not high resolution capable, the `al_get_monitor_info` returns the virtual monitor sizes, so it sounds like we should fix...

Heh, okay that's good to know. If we take the perspective of #923, then Windows behavior is fine and OSX is the one that's broken. We just need to decide...

This bug is there because back in the day we used font flags (via `al_load_font_flags`) for to pass this flag in. I think we should also check the `font_data->bitmap_flags`, just...

There's this pull request which lists audio devices: https://github.com/liballeg/allegro5/pull/1238 I don't know if it works w/ RPI, but if it does, we could add an option to select which audio...

What does `al_get_pixel` return on one of the black regions of your screen?

That's a D-syntax, but in C/C++ you can use `{0, 0, 0, 1}` or w/e other struct initializer syntax. `ALLEGRO_COLOR` has all of its fields public. As for this issue,...

Interesting! So I wonder if the error in the thread is caused by the OpenGL driver not being enabled in Buster Lite, which means that there's technically nothing to do...