wxGLCanvas: empty (default) constructor

[mathieu]

On Feb 1, 9:46 am, CarstenFu... at T-Online.de (Carsten Fuchs) wrote:
> Hi Mathieu,
>
> mathieu wrote:
> > fine now. So whatever issues I had in the past that make me use a
> > wxGLCanvas instead of a wxWindow is gone.
>
> >     * Support wxGTK 2.8.0. wxGTK will now use wxWindow in wxGTK 2.8.0
> > and above. Thus you do not need to compile with opengl support anymore
> > now,
>
> I'm a bit confused: even though you don't use OpenGL with your project, you used a wxGLCanvas
> before? Or vice versa, you do use OpenGL and it happens to work within a regular wxWindow now (where
> a wxGLCanvas used to be used)?  If the latter, that's certainly not portable...

Carsten,

   Do you have some time to answer a couple of question then ? I am
working on wxVTK. Basically it creates a wxWindow, extract the XWindow
pointer and pass it to VTK for rendering. It is working perfectly when
using wxGLCanvas (pre 2.8.0 because of previously described issue).
But if I now switch to wxWindow I can see a couple of minor issues:
- When the first OnPaint occur the image is not displayed correctly.
- When I move another window on top of my wxVTK window and then remove
it. The display is scrambled (not redrawn correctly).

  If you are an expert in the difference in between wxwindow (MSW) and
wxwindow (GTK) (which seems to be the same difference as a
wxGLCanvas(GTK) and wxwindow(GTK)). Could you please let me know how
to deal with them ?

For more info:
http://wxvtk.cvs.sourceforge.net/*checkout*/wxvtk/wxVTK/src/wxVTKRenderWindowInteractor.h
http://wxvtk.cvs.sourceforge.net/*checkout*/wxvtk/wxVTK/src/wxVTKRenderWindowInteractor.cxx

Or the python version which exhibit the same issues:
http://www.vtk.org/cgi-bin/viewcvs.cgi/*checkout*/Wrapping/Python/vtk/wx/wxVTKRenderWindowInteractor.py


Thanks in advance,
Mathieu