sammie381
10-31-2008, 10:11 PM
Why would calling:
wglMakeCurrent( NULL, NULL );
return GL_INVALID_OPERATION, when the previous GL command returned no error?
And it didn't just return one error, it returned thousands of GL_INVALID_OPERATION error messages.
Is there a limit to how many error codes that glGetError() can store? How would I reset it if I wanted to?
[edit]
I just looked at it again, and it's returning an ENDLESS loop of GL_INVALID_OPERATION error messages.
Why would it do something like this? I thought this removes them:
GLenum error;
while ((error = glGetError()) != GL_NO_ERROR) {
// display error
}
wglMakeCurrent( NULL, NULL );
return GL_INVALID_OPERATION, when the previous GL command returned no error?
And it didn't just return one error, it returned thousands of GL_INVALID_OPERATION error messages.
Is there a limit to how many error codes that glGetError() can store? How would I reset it if I wanted to?
[edit]
I just looked at it again, and it's returning an ENDLESS loop of GL_INVALID_OPERATION error messages.
Why would it do something like this? I thought this removes them:
GLenum error;
while ((error = glGetError()) != GL_NO_ERROR) {
// display error
}