Ray
Ray
I decided not to merge this change, a mandatory `rlSetTexture(rlGetTextureIdDefault());` does not look good to me.
@terenctbrobots Yeah, return values should be reviewed: https://github.com/raysan5/raygui/issues/402
> I can close my other window system related issues to not bloat the issue section. @SoloByte Yes, please, I'm a bit overwhelmed with so many window-related issues and discussions....
@CodingMadness the was a closed PR because the amount of changes was too big to manage. Strategy should probably be reviewed and move to user side HighDPI management as much...
@sleeptightAnsiC `GuiTabBar()` was quickly added for convenience for one of my tools and I'm aware it's not much flexible at the moment. > 1.the width of every entry is hard-coded...
Just note that I do not maintain the CMake build system...
@spartan-engi thanks for the review. About the specific function, note that raylib API has no file-format-specific function.
@spartan-engi I'm cosnidering removing SVG support all together...
I decided to remove SVG support from raylib and move the required code to a separate example, the `LoadImageSvg()` API is ugly (and the only format-dependant function in the raylib...
@Falconerd Thanks for reporting, it seems it could be related to ARch Linux but I'm afraid I don't have a paltform configured to review it. If anyone could confirm if...