Re: [PyOpenGL-Users] GLUError and gluNurbsCurve

[Mike C. F. <mcf...@vr...>]

Ivo Ugrina wrote:
> Mike C. Fletcher wrote:
>   
>> Can you give me some details as to what you mean by "bad arguments"?  Do
>> you mean values that are logically inconsistent (don't match the
>> mathematics)?  Or wrong enumerants/invalid options?
>>     
>
> For example 5 points of control polygon and
> order 13 should raise exception GLUError, "too few knots"
> or when I give a decreasing knot sequence it
> should raise exception GLUError, "decreasing knot sequence"
>
> Here is a part of Knotvector::validate
> from sgi implementation of glu (knotvector.cc)
>   
Hmm, are you saying those ints are supposed to be returned as values 
from gluNurbsCurve?  My manual says that it is supposed to have a void 
return type.  Or is this supposed to show up in a glGetError return 
value?  Basically I'm wondering whether these are supposed to be part of 
GLU or part of the wrapper?  If they are part of GLU I don't yet know 
how to retrieve them.

For now, I've added them to the wrapper and have them controlled by 
OpenGL.ERROR_CHECKING, so you can turn them off when your code is no 
longer producing invalid values and want to reclaim the performance.  
You should be able to check out current head via:

    bzr branch lp:pyopengl

and check that the code now catches your errors.

Thanks for the bug report,
Mike

-- 
________________________________________________
  Mike C. Fletcher
  Designer, VR Plumber, Coder
  http://www.vrplumber.com
  http://blog.vrplumber.com