Ok, I think I've found the problem with
It is to do with the way that decrementPointerLock is
used. It calls glGetPointerv when there has not been
any pointers supplied. Thus it raises a gl error.
Not sure why this doesn't happen with
Not sure how the memory management is supposed to
work, so I haven't been able to fix it without it
leeking memory all over the place.
There is a memory leek with no changes as well. You
can see it in the tests that use the gl*Pointer
functions( just move the window arround so that the
display ticks round ).
I don't know the c python api very well, so it would
be good if someone who did could come along and fix
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts