I would like to remove the glReportError call at the end of the render cycle. It doesn't give any useful error to the end user and seems to be freaking people out.
I can see the use for debugging code but not for error reporting.
On Jan 4, 2007, at 1:27 PM, chris clepper wrote:
I would like to remove the glReportError call at the end of the render cycle. It doesn't give any useful error to the end user and seems to be freaking people out.
I can see the use for debugging code but not for error reporting.
...I'd rather not remove it, but maybe have it exposed with the "debug 0/1" message to [gemwin]...I've found it extremely useful when creating patches with the gl wrappers...
jamie
On 1/5/07, james tittle tigital@mac.com wrote:
...I'd rather not remove it, but maybe have it exposed with the "debug 0/1" message to [gemwin]...I've found it extremely useful when creating patches with the gl wrappers...
That is a reasonable solution to me since glGetError is designed for debugging.
Another idea would place debugging in one of the Gem base classes that would turn debugging on and off per object or globally. I have no idea how well that would work in practice but having a message like 'sphere: GL error' or something along that line would be more informative.
cgc
-
chris clepper -
james tittle