Sam Lantinga

> ### API ideas > TTF_SetFontFeatures(font, "calt liga=1 -kern ss01 aalt[3:5]=2"); // space-separated features > TTF_SetFontVariations(font, "wght=500 slnt=-7.5"); // space-separated variations > (the format for each feature/variation are just what...

> I'm not clear on what you mean here. What do you mean by independent? That if we've called `TTF_SetFontFeatures`, `TTF_SetFontKerning` should be ignored? (if so, should calling `TTF_SetFontFeatures(font, NULL)`...

@Martin-Eriksson, I'd like to wrap up an SDL_ttf release, what's the status of this PR? We can definitely add these functions later, but if you'd like to get them in,...

> Thanks for checking! > > I pushed this fix to all main and release branches of all SDL satellite projects. Thanks!

Yeah, it's probably just a math issue in SDL_render.c when calculating the output area. Can you provide a simple example that we can use to repro and verify the fix?

Here's an updated test application that lets you see the black bars during the resize operation: ```c #include #define SDL_MAIN_USE_CALLBACKS #include static SDL_Window *window; static SDL_Renderer *renderer; SDL_AppResult SDL_AppInit(void **appstate,...

@Kaktus514 is correct, when resizing a window you can't maintain the exact pixel ratio unless you do stepwise resizing, which isn't a user experience that people would expect. SDL is...

SDL_LOGICAL_PRESENTATION_STRETCH shows the correct content at all window sizes, and is roughly equivalent to your current workaround. You can use that mode in the example program above to see this...

If you have an idea of how to better handle a window width of 1919, I'd love to hear it. :)

Let's take a very simple example. Let's say your content is a 2x1 block of pixels and you've constrained your aspect ratio at 2. Let's say your window is 2x1....