wxvtk-users

[wxVTK] GTK2 issue

[David J. <dav...@go...>]

Since using wxVTK 1.2 the widget is often not repainted correctly, e.g.
after moving any window in front of the widget and setting the focus to the
wxApp. This happens not only with complex applications, but also with your
samples.

Any suggestions how to get things done?

Dave
--------
Ubuntu 6.10
GTK 2.10.6
wxVTK 1.2
wxWidgets 2.8

Re: [wxVTK] GTK2 issue

[Mathieu M. <mat...@gm...>]

<notetomyself>
Do not touch wxVTK while having the flu, I am doing stupid change.
</notetomyself>

Hi David,

  Yeah I did not fully test my changes. So for now just assume wxVTK
is not compatible with wxGTK 2.8.0.

I'll try to find out a way to fix this mess:
1. Either go back to using a wxGLCanvas
2. Try to figure out what is the issue with focus and enter/leave
event when using a wxWindow

Sorry for troubles
Mathieu


On 2/1/07, David Jany <dav...@go...> wrote:
> Since using wxVTK 1.2 the widget is often not repainted correctly, e.g.
> after moving any window in front of the widget and setting the focus to the
> wxApp. This happens not only with complex applications, but also with your
> samples.
>
> Any suggestions how to get things done?
>
> Dave
> --------
> Ubuntu 6.10
> GTK 2.10.6
> wxVTK 1.2
> wxWidgets 2.8
>
>
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job
> easier.
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
>
> _______________________________________________
> Wxvtk-users mailing list
> Wxv...@li...
> https://lists.sourceforge.net/lists/listinfo/wxvtk-users
>
>
>


-- 
Mathieu

Re: [wxVTK] GTK2 issue

[Wesley B. <wes...@gm...>]

Dear Users,

Is this the same problem I'm having? I guess I'm running the latest
version of GTK as I keep the machine updated frequently using the
package updater on KDE. I've just found this forum after posting the
messgage bellow on the vtk users forum:

Dear Users,

I'm trying to use wxVTKRenderWindow but not having much luck;

>>>python wxVTKRenderWindow.py

(python:5168): Gtk-CRITICAL **: gtk_widget_set_colormap: assertion
`!GTK_WIDGET_REALIZED (widget)' failed

I tried to run the file and I got the above warning, the application
runs, but the picker doesn't work. I've also tried to include a wxVTK
window in a wxPython application. The window veiws the part, and I can
get most interaction with the window, but the picker doesn't work.
When I print out the co-ordinates caught by the pick event I get a
very wrong coordinate such as (11777728 , 0). The picker mothod does
get the right size of window though, in this instance (703 304).

I've just downloaded the latest version of the script from:
http://public.kitware.com/cgi-bin/cvsweb.cgi/VTK/Wrapping/Python/vtk/wx/

I'm running linux FC5, Python 2.4.3 (#1, Oct 23 2006, 14:19:45) [GCC
4.1.1 20060525 (Red Hat 4.1.1-1)] on linux2 with VTK 5.0.2 and
wxPython-2.6.3.2.

Thanks for any help you can offer.

Yours Faithfully,

Wesley Brooks

Since this messgage I checked it on a collegues windows machine and
the picker seemed to work fine.

Yours Faithfully,

Wesley Brooks.

On 03/02/07, Mathieu Malaterre <mat...@gm...> wrote:
> <notetomyself>
> Do not touch wxVTK while having the flu, I am doing stupid change.
> </notetomyself>
>
> Hi David,
>
>   Yeah I did not fully test my changes. So for now just assume wxVTK
> is not compatible with wxGTK 2.8.0.
>
> I'll try to find out a way to fix this mess:
> 1. Either go back to using a wxGLCanvas
> 2. Try to figure out what is the issue with focus and enter/leave
> event when using a wxWindow
>
> Sorry for troubles
> Mathieu
>
>
> On 2/1/07, David Jany <dav...@go...> wrote:
> > Since using wxVTK 1.2 the widget is often not repainted correctly, e.g.
> > after moving any window in front of the widget and setting the focus to the
> > wxApp. This happens not only with complex applications, but also with your
> > samples.
> >
> > Any suggestions how to get things done?
> >
> > Dave
> > --------
> > Ubuntu 6.10
> > GTK 2.10.6
> > wxVTK 1.2
> > wxWidgets 2.8
> >
> >
> > -------------------------------------------------------------------------
> > Using Tomcat but need to do more? Need to support web services, security?
> > Get stuff done quickly with pre-integrated technology to make your job
> > easier.
> > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> >
> > _______________________________________________
> > Wxvtk-users mailing list
> > Wxv...@li...
> > https://lists.sourceforge.net/lists/listinfo/wxvtk-users
> >
> >
> >
>
>
> --
> Mathieu
>
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier.
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Wxvtk-users mailing list
> Wxv...@li...
> https://lists.sourceforge.net/lists/listinfo/wxvtk-users
>

Re: [wxVTK] GTK2 issue

[Mathieu M. <mat...@gm...>]

On 2/3/07, Wesley Brooks <wes...@gm...> wrote:
> Dear Users,
>
> Is this the same problem I'm having? I guess I'm running the latest
> version of GTK as I keep the machine updated frequently using the
> package updater on KDE. I've just found this forum after posting the
> messgage bellow on the vtk users forum:
>
> Dear Users,
>
> I'm trying to use wxVTKRenderWindow but not having much luck;
>
> >>>python wxVTKRenderWindow.py
>
> (python:5168): Gtk-CRITICAL **: gtk_widget_set_colormap: assertion
> `!GTK_WIDGET_REALIZED (widget)' failed

Have you seen this bug for wxWidgets lib:

https://sourceforge.net/tracker/?func=detail&atid=109863&aid=1597527&group_id=9863

...
Hello.

When use wxGlCanvas with wxGTK build, I have a gtk assertion :
Gtk-CRITICAL **: gtk_widget_set_colormap: assertion
`!GTK_WIDGET_REALIZED (widget)' failed

The alone use of gtk_widget_set_colormap function (for wxGTK2 build)
is src/gtk/glcanvas.cpp:339.
In gtk documentation [1], it is specified that this function must be
called before the widget is realized however in the wxGLCanvas::Create
function, it calls wxWindow::Create (l325) which
(src/gtk/window.cpp:2394) shows it.

When I suppress gtk_widget_set_colormap call, assertion is not shoewd
anymore and nothing is affected.
...

Unfortunately nobody answered it. The real issue here is that API of
wxGLCanvas really changed so I am not sure the bug really affect
2.8.0, thus I do not believe wx-deve team will be interested in
solving it. My main goal here is really to try to move toward a common
implementation for msw and gtk (by using wxWindow in both case instead
of wxGLCanvas)....Hopefully solving all those weird issues.

HTH
-M

Re: [wxVTK] GTK2 issue

[Mathieu M. <mat...@gm...>]

On 2/3/07, Mathieu Malaterre <mat...@gm...> wrote:
> On 2/3/07, Wesley Brooks <wes...@gm...> wrote:
> > Dear Users,
> >
> > Is this the same problem I'm having? I guess I'm running the latest
> > version of GTK as I keep the machine updated frequently using the
> > package updater on KDE. I've just found this forum after posting the
> > messgage bellow on the vtk users forum:
> >
> > Dear Users,
> >
> > I'm trying to use wxVTKRenderWindow but not having much luck;
> >
> > >>>python wxVTKRenderWindow.py
> >
> > (python:5168): Gtk-CRITICAL **: gtk_widget_set_colormap: assertion
> > `!GTK_WIDGET_REALIZED (widget)' failed
>
> Have you seen this bug for wxWidgets lib:
>
> https://sourceforge.net/tracker/?func=detail&atid=109863&aid=1597527&group_id=9863
>
> ...
> Hello.
>
> When use wxGlCanvas with wxGTK build, I have a gtk assertion :
> Gtk-CRITICAL **: gtk_widget_set_colormap: assertion
> `!GTK_WIDGET_REALIZED (widget)' failed
>
> The alone use of gtk_widget_set_colormap function (for wxGTK2 build)
> is src/gtk/glcanvas.cpp:339.
> In gtk documentation [1], it is specified that this function must be
> called before the widget is realized however in the wxGLCanvas::Create
> function, it calls wxWindow::Create (l325) which
> (src/gtk/window.cpp:2394) shows it.
>
> When I suppress gtk_widget_set_colormap call, assertion is not shoewd
> anymore and nothing is affected.
> ...
>
> Unfortunately nobody answered it. The real issue here is that API of
> wxGLCanvas really changed so I am not sure the bug really affect
> 2.8.0, thus I do not believe wx-deve team will be interested in
> solving it. My main goal here is really to try to move toward a common
> implementation for msw and gtk (by using wxWindow in both case instead
> of wxGLCanvas)....Hopefully solving all those weird issues.

BTW Changing
WX_USE_GLCANVAS = 1
into
WX_USE_GLCANVAS = 0

work around this issue. But as other people mentionned before, you'll
have some issue on the first render, and when moving a window on top
of the wxVTK window.

:(
-M

Re: [wxVTK] GTK2 issue

[Wesley B. <wes...@gm...>]

Thanks for your help, apollogies for the delay in replying I've been
side tracked!

>BTW Changing
>WX_USE_GLCANVAS = 1
>into
>WX_USE_GLCANVAS = 0

In my version of wxVTKRenderWindow.py that line isn't there, however
adding the line doesn't seem to brake anything, but equally doesn't
fix much! I did find the following at the top of the file:

if wx.Platform == "__WXGTK__":
    import wx.glcanvas
    baseClass = wx.glcanvas.GLCanvas

Commenting out these lines did get rid of the segmentation fault,
however it did not fix the picker problem. It's still getting crazy
coordinates which would place the mouse cursor at the top of the
screen and a few offices to my right!

I'm currently having a look to see if there are any RPMs avaliable of
a more up to date version of wxPython/wxGTK. My software is the most
up to date avaliable through FC5 software updater.

Thanks again for the help,

Wesley Brooks.

Python 2.4.3 (#1, Oct 23 2006, 14:19:45)
wxPython-2.6.3.2
wxGTK-2.6.3
VTK-5.0.2




On 03/02/07, Mathieu Malaterre <mat...@gm...> wrote:
> On 2/3/07, Mathieu Malaterre <mat...@gm...> wrote:
> > On 2/3/07, Wesley Brooks <wes...@gm...> wrote:
> > > Dear Users,
> > >
> > > Is this the same problem I'm having? I guess I'm running the latest
> > > version of GTK as I keep the machine updated frequently using the
> > > package updater on KDE. I've just found this forum after posting the
> > > messgage bellow on the vtk users forum:
> > >
> > > Dear Users,
> > >
> > > I'm trying to use wxVTKRenderWindow but not having much luck;
> > >
> > > >>>python wxVTKRenderWindow.py
> > >
> > > (python:5168): Gtk-CRITICAL **: gtk_widget_set_colormap: assertion
> > > `!GTK_WIDGET_REALIZED (widget)' failed
> >
> > Have you seen this bug for wxWidgets lib:
> >
> > https://sourceforge.net/tracker/?func=detail&atid=109863&aid=1597527&group_id=9863
> >
> > ...
> > Hello.
> >
> > When use wxGlCanvas with wxGTK build, I have a gtk assertion :
> > Gtk-CRITICAL **: gtk_widget_set_colormap: assertion
> > `!GTK_WIDGET_REALIZED (widget)' failed
> >
> > The alone use of gtk_widget_set_colormap function (for wxGTK2 build)
> > is src/gtk/glcanvas.cpp:339.
> > In gtk documentation [1], it is specified that this function must be
> > called before the widget is realized however in the wxGLCanvas::Create
> > function, it calls wxWindow::Create (l325) which
> > (src/gtk/window.cpp:2394) shows it.
> >
> > When I suppress gtk_widget_set_colormap call, assertion is not shoewd
> > anymore and nothing is affected.
> > ...
> >
> > Unfortunately nobody answered it. The real issue here is that API of
> > wxGLCanvas really changed so I am not sure the bug really affect
> > 2.8.0, thus I do not believe wx-deve team will be interested in
> > solving it. My main goal here is really to try to move toward a common
> > implementation for msw and gtk (by using wxWindow in both case instead
> > of wxGLCanvas)....Hopefully solving all those weird issues.
>
> BTW Changing
> WX_USE_GLCANVAS = 1
> into
> WX_USE_GLCANVAS = 0
>
> work around this issue. But as other people mentionned before, you'll
> have some issue on the first render, and when moving a window on top
> of the wxVTK window.
>
> :(
> -M
>