Colleague Riley Mabb
Colleague Riley Mabb
Ok, I think I've said most of what I want to say on this. I can help with the platform part.
@Bigfoot71 You should include some way to use BGR or RGB. BGR is better for performance in most cases. X11, for example, does not have a way to render BGR...
I think Winapi uses bitmasking and it has performance issues. It might be better to change it on compile time. I'm not 100% sure, I've not tested that directly. eg....
Definitionally seems like an oversight. RGFW 1.8.0 is currently not accepting new features, it's in a testing stage. This should be added in 1.8.5.
Most systems will provide the monitor's refresh rate directly, so it's better to go based on that.
I don't think that suggestion makes much sense in relation to a monitor's refresh rate. I don't think limiting the FPS based on a target frame time is a good...
@mpalomas I'm not sure how practical this would be. The X11 function `XRRConfigCurrentRate` you mentioned outputs a short, as seen in the example you mentioned and Windows does not give...
Although the solution seems sketchy, I think it's worth implementing. Sadly I don't think there is a better solution. This issue should probably be moved over to the RGFW repo.
@nicbarker Either using `void*` or `size_t` would be a potential solution. Another solution could be: ```c #ifndef CLAY_FONT_ID #define CLAY_FONT_ID u16 #endif ``` This would allow users to use whatever...
@FintasticMan Yes, I think that's about the same as `size_t` except that it's explicitly intended for pointers. So it would probably be better to use `intptr_t`.