#43 gl*Pointer not usable with Numeric-22.0

v2.0
closed-fixed
GL (74)
5
2003-01-19
2002-10-16
No

After a very long debugging session, I found that
Numeric-22.0 appears to break all code that uses
gl*Pointer, resulting in either no geometry, or
an "Application Error".

Simply reverting back to Numeric-21.3 restores code to
working order.

Behavior was verified with various demos provided in
both PyOpenGL and PyOpenGLContext, including:
OpenGL\Demo\da\dots.py
OpenGL\Demo\tom\arraytest.py
OpenGL\Demo\tom\poly.py
OpenGLContext\tests\gldrawarrays.py

#~ Start code example ~~~~~~~~~
Verticies = Numeric.transpose([Numeric.arange
(0.,1.,1./1000., Numeric.Float)]*3)

glPushClientAttrib(GL_CLIENT_VERTEX_ARRAY_BIT)
glVertexPointerd(Verticies)
glEnableClientState(GL_VERTEX_ARRAY)
glDrawArrays(GL_POINTS, 0, len(Verticies))
glPopClientAttrib()
#~ End code example ~~~~~~~~~

System Configuration:
Windows 2000 & XP
Numeric 22.0
Python 2.2.2 & 2.2.1
PyOpenGL 2.0

Discussion

  • Shane Holloway

    Shane Holloway - 2002-10-16

    Logged In: YES
    user_id=283742

    Config Note:
    PyOpenGL 2.0.0.44 from the SourceForge Files area

     
  • Shane Holloway

    Shane Holloway - 2002-10-16

    Logged In: YES
    user_id=283742

    Works with current version (2.0.1.47.a1) from CVS and
    Numeric-22.0.

    Perhaps the WinInstallers should be labeled with the version
    number of Numeric it was built with as well?

     
  • Mike C. Fletcher

    Logged In: YES
    user_id=34901

    I'm going to mark this "fixed" as it is known to work with
    the matching Numeric versions (i.e. pre-22 vs. 22+). Since,
    at the moment, we don't have binary builds, the
    marking-with-numeric-version question seems moot.

     
  • Mike C. Fletcher

    • assigned_to: nobody --> mcfletch
    • status: open --> closed-fixed
     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks