After RGFW update to 2.0.0-dev in fbd83cafc7, RGFW_window_setIcon api has changed -- not it takes pixel format enum instead of number of channels. On raylib side it was still passing 4 (number of channels in rgba) which is enum value for BGRA8. Instead we have to pass 2 now (RGFW_formatRGBA8 = 2).
* RGFW also requires RGBA8 images as window icons, as raylib already reports in raylib.h
* LibraryConfigurations.cmake: exchanged MATCHES -> STREQUAL in platform choosing if-statements
* WebRGFW: remapping mouse/touch position to canvas pixel coordinates
* fix 'typo'
* has to be done like that because of += in case of captured mouse
* [rcore_desktop_rgfw] [emscripten] fix typo
* RGFW also requires RGBA8 images as window icons, as raylib already reports in raylib.h
* LibraryConfigurations.cmake: exchanged MATCHES -> STREQUAL in platform choosing if-statements
* WebRGFW: remapping mouse/touch position to canvas pixel coordinates
* fix 'typo'
* has to be done like that because of += in case of captured mouse
* Testing linux implementation
* Add implementation for ClipboardImage on Linux
* Adding another check to make sure that only X11 include X11 libs
* Adding some comments to explain the magic numbers
[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.
* use FLAG_* macros where possible
* rename `FLAG_CHECK()` to `FLAG_IS_SET()`
* remove unnecessary equality checks
* fix issues
---------
Co-authored-by: Ray <raysan5@gmail.com>
Restore window currently says it sets the window state to:
"not minimized/maximized"
However, if a window is maximized and then minimized, it's typical that
it would restore back to being maximized, which is what seems to happen
from my testing. I've reworded the description to better reflect
this behavior.
