It's full of useless features - too retarded-friendly, like everything tends to become over time.
Well, there's notepad.exe
; knock yourself out. As un-userfriendly as it gets.
Why would one use two versions of GLFW in the same application? It's all the same crap.
You wouldn't use two different versions of a library in the same application, silly! If you have ever developed more than one application, then using the "latest" version of a library at the times of both applications' development are going to be different. Including glfw.h
in the application developed years earlier is going to break when you change your environment's paths to always use the latest versions of your libraries. (Again, with Visual Studio's property pages, this is possible.)
Too retarded-friendly (like everything tends to become over time) and I couldn't find 2.7.7's documentation.
The newest version of glfw I downloaded came included with the documentation; even 2.7.7
had documentation! glfw-2.7.7.bin.WIN32.zip\glfw-2.7.7.bin.WIN32\docs\
I was talking about the name of the function, which is stupid. It's the first time I see the word 'should' in a program.
You can use a macro to hide it, if you really want to. You could even comment it!
// Wow, I'd rather rebuild an entire cross-platform library than to use the word "should" in a program.
#define glfwWindowIsOpen(window) (!glfwWindowShouldClose(window))
Edited by fastcall22, 28 October 2013 - 04:06 PM.