[PyOpenGL-Users] Re: [wxPython-users] Multiple wxGLCanvas in one process

[Mike C. F. <mcf...@ro...>]

Can't really give much help without considerably more information (such 
as *what* is showing up as shared between the contexts).  It's 
definitely possible to run multiple OpenGL contexts within a wxPython 
application, at least in my limited testing.  I've attached a script 
which creates two independent OpenGLContext contexts within the same 
frame.  OpenGLContext is fairly anal about making sure everything occurs 
within SetCurrent calls, but you say you're doing that already.

That said, I very seldom actually create multiple contexts, so they 
don't get tested much by *me*, so there may be an error in how PyOpenGL 
is handling the contexts (e.g. it may have an error in the array-pointer 
management).  (Would be helpful to know PyOpenGL version, platform, and 
graphics card for tracking down such a problem, (a test-case showing the 
problem tends to make debugging & fixing go much faster too ;) )).

BTW, probably best to ask these kinds of questions on the PyOpenGL list, 
as OpenGL isn't really a *common* thing (AFAIK) in which wxPython people 
specialise, (and most likely this is going to be an OpenGL (possibly 
usage) error, rather than anything to do with wxPython).

Good luck,
Mike

Luc Bourhis wrote:

> I've run into an insoluble problem with wxPython (2.5.x release). I 
> have created a widget containing 2 instances of classes derived from 
> wxGLCanvas: they seem to share at least part of the OpenGL context. I 
> do call SetCurrent in a timely manner, first thing after catching the 
> "paint" and the "resize" event, before any actual drawing or resizing. 
> But it is still rather obvious there is interference between the both 
> of these instances.
>
> Any pointer? I cannot find any reference to such an issue on the 
> mailing lists.

________________________________________________
  Mike C. Fletcher
  Designer, VR Plumber, Coder
  http://www.vrplumber.com
  http://blog.vrplumber.com