Colleague Riley Mabb

It seems like it's related to the `RGFW_windowNoResize` flag.

This problem also occurs for `examples/basic/basic`, so it's not just a software rendering issue. 

This only happens when the `RGFW_windowNoResize` flag is applied. It is strange that in your screenshot, the `examples/buffer/buffer` example has this issue. When it doesn't use that flag.

It seems that `RGFW_windowNoResize` made it so the window didn't include the `WS_THICKFRAME` flag. This issue should be fixed with the latest commits.

I'm unable to replicate the bug. (On the larger 1920x1080 primary screen with 125% scaling.)  (On the smaller 1366x765 secondary screen with 100% scaling)  With extended displays, both...

I was able to test the same monitor arrangement and I was still unable to recreate the issue. Are you sure that was done using the newest version of RGFW?

I'm closing this issue because it has been unable to be recreated and it has been left stagnant for some time. If there are any updates or anyone is able...

@RobLoach This is a problem for each platform as far as I can tell. Dear ImGUI handles it with imgui_opengl.h and imgui_.h Where the graphics API platform can work with...

@xroberx > RGFW seems to be terribly broken What specifically is broken? > HOWEVER, now I cannot use SetWindowSize() after InitWindow(), it is just ignored. That's strange, I'll look into...

@xroberx Do you mind opening the RGFW issue separately so I can look into it?