bug in _glTexCoordPointer
Brought to you by:
mcfletch
_glTexCoordPointer calls
decrementPointerLock(GL_TEXTURE_COORD_ARRAY);
instead of
decrementPointerLock(GL_TEXTURE_COORD_ARRAY_POINTER);
causing (inscrutable) runtime errors. Tried to fix
this in the .i file but some of the typemaps are
incompatible with swig 1.3.11u, the version I have
installed.
Logged In: YES
user_id=34901
I'm told this fix is working for some other users already.
I'd prefer a test case to see if the error is fixed after
applying the fix, but the problem appears to be a fairly
straightforward one? so might just go ahead and do the fix.
Logged In: YES
user_id=2042
Tried changing it to GL_TEXTURE_COORD_ARRAY_POINTER in a
test app and it does not work. The app works with some code
from the 1.5x pyopengl distrib. I'm looking at a fix some
more tommorow, after some sleep :)
Logged In: YES
user_id=34901
Andy Sy (apparently the original submitter) gave a test app
on the PyGame list, so I went ahead and applied the change
to the CVS repository version. There was one other case
where a decrementPointerLock call is made on something not
explicitly called a "pointer", but that seems to be
legitimate (it's the Sun triangle.i extension).
Testing script for texture coordinate pointer failure, if bug is present, will bomb out with invalid operation error before starting, otherwise (assuming it gets all the sounds loaded) will display a screen.
Logged In: NO
I am not using swig at all and the fixing works excellent.