I've just discovered yet another "how can that possibly not work" issue
with wxPython + PyOpenGL under RHLinux 8.0, which is making me wonder:
* Does wxGLCanvas just not work on Linux?
o Has anyone else really used it (not just running the demos,
actually used it, doing any of the things decribed below)?
o Did you discover and work around these problems (described
o Did the problems not show up at all?
* Is there something wrong with how I'm doing SetCurrent() for the
o I'm just calling wxGLCanvas.SetCurrent(), which AFAICS is
the correct thing to do.
Basically, here are the things that are not working:
* Display-lists can't be generated, glGenLists always returns 0
* glInitMultitextureARB returns 0 under wxPython contexts, but 1 for
GLUT contexts (same machine, same everything else). In other
words, the extension isn't recognised for wxPython contexts but is
for GLUT contexts
* gluBuild2DMipmaps seg-faults under wxPython, works fine under GLUT
The symptoms would all suggest that (Py)OpenGL isn't recognising the
current context (display-lists are context-specific, as are extensions
and texture-objects), but I can't imagine what would cause such a thing
in my code. I've checked, and I'm definitely calling
on the wxGLCanvas instance.
So, I'm wondering, am I just the first person to really use the wxPython
wxGLCanvas? My testing on Linux has never been particularly extensive,
but I can't imagine that anyone really using wxGLCanvas on this platform
hasn't noticed such an effect.
Oh, same code, same versions of wxPython and PyOpenGL works fine on
Win2K, and as noted above, all the code works fine with the GLUT
contexts on Linux (and Win2K).
So, is this an isolated incident, or am I tredding upon new ground here?
Mike C. Fletcher
Designer, VR Plumber, Coder