| Wouldn't a technically clean solution consist in storing the
| Python exception
| information in a global somewhere, and raise the opengl error
| indicator with a
| Python-specific value upon returning from the Python callback when
| PyErr_Occurred(), so that this 'Glenum PyOpenGLError' code be
| retrieved later
| with the glGetError() function by whomever wishes to catch the error ?
No because, one can't exit from glutMainLoop except by sys.exit
| But what if glGetError() gets raise in the event loop ?
| Shouldn't this be catched, without regard to the origin of the glError ?
| If this were the case, glutMainLoop should also check for glGetError()...
glutMainLoop does get checked for glGetError, but this check is useless
since glutMainLoop never returns.
Anyways, the debate is not over glGetError, but Python exceptions.
Get latest updates about Open Source Projects, Conferences and News.