Closed Guillaume227 closed 1 year ago
Hello,
Thanks for this. A PR would be perfect! concerning the unused variable you can silence the warning with `(void)varName;ˋ
What about the glfw_error_callback
warning ? Seems like maybe we forgot to set that callback with glfwSetErrorCallback(glfw_error_callback);
? I am not sure where that statement should go though.
What about the glfw_error_callback warning ? Seems like maybe we forgot to set that callback with glfwSetErrorCallback(glfw_error_callback); ? I am not sure where that statement should go though.
It is unused. I'll remove it.
I have noticed the following warnings when building on windows. Absolutely not critical but I like to have a clean build, so would be nice to get rid of them. Let me know if you would like a PR or just handle them on your end when time permits.
Commenting out the parameter name should do for those:
Not sure about that one:
That one is probably a release vs debug thing: the value is used by an assert macro that does not do anything in release.
A static_cast should be ok for that one (although that's 3rd party code):