235 2006-07-09 09:32:03 +0200 VBO with GL glVertexPointer with a null array 2010-03-24 07:49:19 +0100 0 0 3 JogAmp Jogl core 1 All all VERIFIED WONTFIX P3 normal --- 1 sgothel sgothel DEFECT --- oldest_to_newest 251 0 sgothel 2010-03-24 07:49:19 +0100 ---- Reported by aaronanderson 2006-07-09 21:32:03 ---- On the JOGL GL interface there are two glVertexPointer method signatures: void glVertexPointer(int size, int type, int stride, Buffer ptr) void glVertexPointer(int size, int type, int stride, long ptr_buffer_offset) If I issue a glBindBufferARB() right before a call to glVertexPointer( 3, GL.GL_DOUBLE, 0, (Buffer)null ); I get an exception: Exception in thread "Thread-2" javax.media.opengl.GLException: javax.media.opengl.GLException: array vertex_buffer_object must be disabled to call this method at javax.media.opengl.Threading.invokeOnOpenGLThread(Threading.java:271) at javax.media.opengl.GLCanvas.maybeDoSingleThreadedWorkaround (GLCanvas.java:256) at javax.media.opengl.GLCanvas.display(GLCanvas.java:130) at com.sun.opengl.util.Animator.display(Animator.java:144) at com.sun.opengl.util.Animator$MainLoop.run(Animator.java:181) at java.lang.Thread.run(Thread.java:619) However if I change the call to glVertexPointer( 3, GL.GL_DOUBLE, 0, 0 ); I don't get an exception and I get the desired results. I believe both calls are equivalent and should be treated the same. ---- Additional Comments From kbr 2006-07-09 23:50:47 ---- These overloaded routines are left distinct because of type safety and security issues. While it is in theory possible to overload the meaning of the version taking a Buffer in the manner described, we are not going to make this change at this time. --- Bug imported by sgothel@jausoft.com 2010-03-24 07:49 EDT --- This bug was previously known as _bug_ 235 at https://jogl.dev.java.net/bugs/show_bug.cgi?id=235