Ray
@Joonsey Ok, let's merge it! Anyway, Zig users should probably update to v0.14 at this point...
@foxblock Those examples are intended to be used from C code, I'm afraid I'm not changing them for a specific use case.
@foxblock Yeah, ellipsis were just added as a graceful overflow visual option for the other controls, never intended for `GuiTextBox()`... Not sure how it should be approached in case of...
@ssoher Yeah, return values should be reviewed: https://github.com/raysan5/raygui/issues/402 But I'd like to review it carefully to find some consistency between all controls.
It seems several comments on this issue were deleted by author making the full thread a bit confusing. There are considerable casuistics involved in getting the current monitor width and...
@sleeptightAnsiC Thanks for reviewing this issue, that's what I see: https://github.com/user-attachments/assets/1e7645ba-68ce-4b77-a682-719d1e9200e6 I think there could be some missunderstanding on my side, afair `GetScreenHeight()` was supposed to return the current framebuffer...
@maiconpintoabreu Yes, but those functions are expected to return the working resolution, set by user, not the internal framebuffer render resolution, that it's usually bigger on HighDPI, neither the current...
@Moros1138 My concern with this change is if it will change examples behaviour between platforms... if that's the case it should be addressed on all platforms.
@Moros1138 Just tested it and it breaks `DisableCursor()` behaviour, you can test `core_3d_camera_first_person`. Please, be careful testing those PRs, there are many platforms and use cases involved and one solution...
Just reviewed required code to add a new state.