* Fix window scaling on Wayland with GLFW 3.4+ display scaling
GLFW 3.4 defaults GLFW_SCALE_FRAMEBUFFER to TRUE on all platforms,
causing framebuffer/window size mismatch on Wayland with display
scaling (content renders in a subset of the window, mouse coordinates
are wrong).
Three fixes:
- Disable GLFW_SCALE_FRAMEBUFFER on Wayland when FLAG_WINDOW_HIGHDPI
is not set, restoring 1:1 window-to-framebuffer mapping
- With FLAG_WINDOW_HIGHDPI, read actual framebuffer size from GLFW
instead of resizing the window (which double-scales on Wayland
where GLFW_SCALE_TO_MONITOR has no effect)
- Skip mouse coordinate scaling on Wayland since GLFW already reports
coordinates in logical (window) space
Tested on NixOS/Niri with GLFW 3.4 at 1x, 1.5x, and 2x scaling.
Fixes#5504
* Fix fullscreen and borderless windowed scaling on Wayland with HiDPI
ToggleFullscreen and ToggleBorderlessWindowed exit paths manually
scale screen size by DPI before passing to glfwSetWindowMonitor,
which double-scales on Wayland where GLFW_SCALE_FRAMEBUFFER already
handles it. Skip the manual resize on Wayland.
Also fix FramebufferSizeCallback fullscreen branch: on Wayland with
GLFW_SCALE_FRAMEBUFFER the framebuffer is still scaled in fullscreen,
so use the logical window size as screen size and derive screenScale
from the framebuffer/window ratio.
Fixes#5504
* Apply style fixes from code review: remove duplicate screenScale assignment, collapse single-statement ifs to one line, remove trailing periods from comments
* fixed typos preventing window from min/maxing
* fixed window style generation ignoring minimize precedence, causing errors in edge cases
* added maximize button on resizable windows
* fixed infinite loop when resizing the window manually
* activate window upon creation to set focus and show taskbar icon
* extended SanitizeFlags() to account for problematic resizing/mizing flag mixups
[utils] was created long time ago, when [rcore] contained all the platforms code, the purpose of the file was exposing basic filesystem functionality across modules and also logging mechanism but many things have changed since then and there is no need to keep using this module.
- Logging system has been move to [rcore] module and macros are exposed through `config.h` to other modules
- File system functionality has also been centralized in [rcore] module that along the years it was already adding more and more file-system functions, now they are all in the same module
- Android specific code has been moved to `rcore_android.c`, it had no sense to have specific platform code in `utils`, [rcore] is responsible of all platform code.
* Improved touch input handling and multitouch support in drm platform
* revert
* made some fixes for the touch issue in drm platform
* updated touch input handling by adding multitouch support
* improved how it handles the multitouch
* added cleanup
* Remove touch last update tracking to simplify touch input handling
* improved multitouch support by tracking touch positions and IDs for each slot
* Better touch input handling
* Increase maximum touch points from 8 to 10 and enhance touchscreen prioritization logic
* Refactor touch input handling to use slot index as ID for stability and simplify touch clearing logic
* Improve touch input handling by activating slot 0 based on mouse click or touch events
* touch event handling to use tracking ID for unique touch identification
* Add multitouch detection to PollMouseEvents for improved touch handling
* Fix conditional formatting in PollMouseEvents for clarity
* Refactor conditional statements in PollMouseEvents and InitPlatform for improved readability
* Fix formatting in PollMouseEvents for improved readability
in android gesture system is not reporting GESTURE_NONE, specified in the issue https://github.com/raysan5/raylib/issues/5010 so, automatically GESTURE_SWIPE, TAP, DOUBLE_TAP, also will not be reported. in this commit it is fixed.
Considering multi-monitor and multi-ppi configurations
Fullscreen-exclusive scales to available display resolution, ignoring content scaling
Windowed-borderless scales to available logical resolution considering HighDPI **if requested**
