Dave Green

@SuperUserNameMan I have already tested it and it improves things. The screen size values are correct and no longer missing a few pixels.

@SuperUserNameMan I have not tested it with the new patch

@SuperUserNameMan @fishbowlforever The window resize callback also calls [SetupViewport](https://github.com/raysan5/raylib/blob/174313acbfa74d2a45fc0207f47ab00fbdb06050/src/rcore.c#L3181C1-L3192C7) which introdues dpi scale again. I don‘t know if that causes any problems though. > What I have found is that...

> > @SuperUserNameMan I have not tested it with the new patch > > ok then, let's start again from a fresh code base then. I agree but just for...

### A Changing/Fixing Borderless Fullscreen Mode to how it is described in the glfw documentation. It is easy to do and does not change a lot. It fixes Borderless Fullscreen...

### B Fixing Fullscreen mode. It works already but there is a few small things. (I have a branch for it and tested it)

### C Enhancing Fullscreen mode. Currently the window size has to be used to set the fullscreen resolution. This means that raylib can not restore the window to the correct...

### D GLFW documentation states that the `WindowSizeCallback()` should NOT be used to set `glViewport()`. Right now the `WindowSizeCallback()` calls `SetupViewport() → rlViewport() → glViewport()` . The framebuffer size instead...

### E Adding a function for getting all supported video modes of a monitor. This is important for fullscreen.  Right now you can only guess as a user of raylib...

### F Remove/disable the high dpi flag for now