Re: [glewpy-users] god dammit, ARB_vertex_buffer_object

[Leonard \paniq\ R. <pa...@pa...>]

self.m_nVBOVertices = glGenBuffersARB(1)
glBindBufferARB( GL_ARRAY_BUFFER_ARB, self.m_nVBOVertices)

gives me:

  File "lesson45.py", line 314, in InitGL
    g_pMesh.BuildVBOs()
  File "lesson45.py", line 215, in BuildVBOs
    glBindBufferARB( GL_ARRAY_BUFFER_ARB, self.m_nVBOVertices )	# //
Bind The Buffer
  File "arb.pyx", line 2021, in arb.glBindBufferARB
TypeError: an integer is required

On Fri, 2005-10-21 at 08:57 -0500, Charles Moad wrote:
> Fixed in the attached.  Let me know if you run into any more issues.
> 
> FYI, glGenBuffers is there with the OpenGL 1.5 support.  I looked at it 
> and I think it was already corrected.  You may want to look into using 
> these functions instead, hence drop the "ARB" suffix.
> 
> - Charlie
> 
> Leonard "paniq" Ritter wrote:
> > glMapBufferARB isnt the problem, and i do not need the map functions for
> > now.
> > 
> > however glGenBufferARB is wrongly implemented. at the moment it needs 2
> > parameters and treats parameter 2 as an input parameter, when its
> > actually an output parameter.
> > 
> > On Thu, 2005-10-20 at 17:04 -0500, Charles Moad wrote:
> > 
> >>Well, it's all there except glMapBufferARB.  This is due the  
> > 
> > fact the method returns a void pointer.  How to handle void pointers  
> > is a tricky subject in python.  It is doable when you know the length  
> > of the data, but at first glance at this function it is not obvious  
> > how to get this length.  It would help greatly if you could send a  
> > sample block of code using these methods.  I could probably add this  
> > functionality fairly fast then.
> > 
-- 
-- leonard "paniq" ritter
-- http://www.mjoo.org
-- http://www.paniq.org