wxvtk-users Mailing List for wxVTKRenderWindowInteractor (Page 2)
Brought to you by:
malat
Menu
▾
▴
wxvtk-users — wxVTK users
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
(7) |
Feb
|
Mar
(2) |
Apr
(12) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(7) |
Nov
(13) |
Dec
|
| 2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(5) |
Jun
(6) |
Jul
(3) |
Aug
(11) |
Sep
|
Oct
(10) |
Nov
(2) |
Dec
(1) |
| 2007 |
Jan
(16) |
Feb
(9) |
Mar
(13) |
Apr
|
May
(7) |
Jun
(8) |
Jul
|
Aug
(14) |
Sep
|
Oct
(6) |
Nov
|
Dec
(1) |
| 2008 |
Jan
(20) |
Feb
(1) |
Mar
|
Apr
(20) |
May
(5) |
Jun
(11) |
Jul
|
Aug
(52) |
Sep
(2) |
Oct
(35) |
Nov
(7) |
Dec
(14) |
| 2009 |
Jan
(4) |
Feb
(5) |
Mar
(9) |
Apr
(19) |
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
(5) |
Dec
|
| 2010 |
Jan
(1) |
Feb
(5) |
Mar
|
Apr
(3) |
May
|
Jun
|
Jul
(4) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(4) |
Dec
(13) |
| 2012 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(9) |
Nov
|
Dec
|
| 2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
(1) |
Dec
|
|
From: Tim H. <tim...@gm...> - 2011-12-01 09:58:50
|
Andrew Trevorrow has committed this fix to our version, to get it working on Cocoa in wxOSX 2.9.x. https://code.google.com/p/reaction-diffusion/source/diff?spec=svn199&r=199&format=side&path=/trunk/ReaDy_gui/wxVTKRenderWindowInteractor.cxx I'm not on MacOS myself but he says it is needed. On 30 November 2011 14:47, Sander Niemeijer <nie...@st...> wrote: > Hi Mathieu, > > I did a quick compare of the current wxVTK CVS with what we are using > internally. There is currently one difference: > The patch below is to fix a redrawing issue we encountered on Windows > when windows got resized. It was something we fixed in September 2009, > so I don't know the precise details anymore. > > I would appreciate it if you could include this patch for v1.4. > > Best regards, > Sander Niemeijer > > --- cvs/wxVTKRenderWindowInteractor.cxx 2009-03-05 17:00:43.000000000 > +0100 > +++ new/wxVTKRenderWindowInteractor.cxx 2009-09-04 11:50:25.000000000 > +0200 > @@ -281,6 +281,9 @@ > Size[1] = y; > // and our RenderWindow's size > RenderWindow->SetSize(x, y); > +#if defined(__WXMSW__) > + this->Refresh(); > +#endif //__WXMSW__ > } > } > } > > > On 30 nov 2011, at 15:10, Mathieu Malaterre wrote: > >> Hi Tim, >> >> Ok will do. I'll do that on Friday. >> >> Everyone, >> >> Last call for integrating your patch in 1.4 release. You'll have to >> wait another ~3yrs or so otherwise ;) >> >> Thanks ! >> >> On Wed, Nov 30, 2011 at 1:03 PM, Tim Hutton <tim...@gm...> >> wrote: >>> Hello, >>> >>> I've just been bitten by the fact that the 1.3 download (from 2008) >>> is >>> older than some of the fixes in the CVS head. Specifically: the Timer >>> error has gone, and the Cocoa build wasn't working. I see there are >>> around 8 downloads a week so presumably all of these people are being >>> hit by these issues too! So please make a new download. >>> >>> And thankyou thankyou thankyou for maintaining wxVTK. I've been using >>> it continuously for several years now. >>> >>> -- >>> Tim Hutton - http://www.sq3.org.uk - http://profiles.google.com/tim.hutton/ >>> >>> ------------------------------------------------------------------------------ >>> All the data continuously generated in your IT infrastructure >>> contains a definitive record of customers, application performance, >>> security threats, fraudulent activity, and more. Splunk takes this >>> data and makes sense of it. IT sense. And common sense. >>> http://p.sf.net/sfu/splunk-novd2d >>> _______________________________________________ >>> Wxvtk-users mailing list >>> Wxv...@li... >>> https://lists.sourceforge.net/lists/listinfo/wxvtk-users >>> >> >> >> >> -- >> Mathieu >> >> ------------------------------------------------------------------------------ >> All the data continuously generated in your IT infrastructure >> contains a definitive record of customers, application performance, >> security threats, fraudulent activity, and more. Splunk takes this >> data and makes sense of it. IT sense. And common sense. >> http://p.sf.net/sfu/splunk-novd2d >> _______________________________________________ >> Wxvtk-users mailing list >> Wxv...@li... >> https://lists.sourceforge.net/lists/listinfo/wxvtk-users > > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure > contains a definitive record of customers, application performance, > security threats, fraudulent activity, and more. Splunk takes this > data and makes sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-novd2d > _______________________________________________ > Wxvtk-users mailing list > Wxv...@li... > https://lists.sourceforge.net/lists/listinfo/wxvtk-users -- Tim Hutton - http://www.sq3.org.uk - http://profiles.google.com/tim.hutton/ |
|
From: Sander N. <nie...@st...> - 2011-11-30 15:05:29
|
Hi Mathieu,
I did a quick compare of the current wxVTK CVS with what we are using
internally. There is currently one difference:
The patch below is to fix a redrawing issue we encountered on Windows
when windows got resized. It was something we fixed in September 2009,
so I don't know the precise details anymore.
I would appreciate it if you could include this patch for v1.4.
Best regards,
Sander Niemeijer
--- cvs/wxVTKRenderWindowInteractor.cxx 2009-03-05 17:00:43.000000000
+0100
+++ new/wxVTKRenderWindowInteractor.cxx 2009-09-04 11:50:25.000000000
+0200
@@ -281,6 +281,9 @@
Size[1] = y;
// and our RenderWindow's size
RenderWindow->SetSize(x, y);
+#if defined(__WXMSW__)
+ this->Refresh();
+#endif //__WXMSW__
}
}
}
On 30 nov 2011, at 15:10, Mathieu Malaterre wrote:
> Hi Tim,
>
> Ok will do. I'll do that on Friday.
>
> Everyone,
>
> Last call for integrating your patch in 1.4 release. You'll have to
> wait another ~3yrs or so otherwise ;)
>
> Thanks !
>
> On Wed, Nov 30, 2011 at 1:03 PM, Tim Hutton <tim...@gm...>
> wrote:
>> Hello,
>>
>> I've just been bitten by the fact that the 1.3 download (from 2008)
>> is
>> older than some of the fixes in the CVS head. Specifically: the Timer
>> error has gone, and the Cocoa build wasn't working. I see there are
>> around 8 downloads a week so presumably all of these people are being
>> hit by these issues too! So please make a new download.
>>
>> And thankyou thankyou thankyou for maintaining wxVTK. I've been using
>> it continuously for several years now.
>>
>> --
>> Tim Hutton - http://www.sq3.org.uk - http://profiles.google.com/tim.hutton/
>>
>> ------------------------------------------------------------------------------
>> All the data continuously generated in your IT infrastructure
>> contains a definitive record of customers, application performance,
>> security threats, fraudulent activity, and more. Splunk takes this
>> data and makes sense of it. IT sense. And common sense.
>> http://p.sf.net/sfu/splunk-novd2d
>> _______________________________________________
>> Wxvtk-users mailing list
>> Wxv...@li...
>> https://lists.sourceforge.net/lists/listinfo/wxvtk-users
>>
>
>
>
> --
> Mathieu
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure
> contains a definitive record of customers, application performance,
> security threats, fraudulent activity, and more. Splunk takes this
> data and makes sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-novd2d
> _______________________________________________
> Wxvtk-users mailing list
> Wxv...@li...
> https://lists.sourceforge.net/lists/listinfo/wxvtk-users
|
|
From: Mathieu M. <mat...@gm...> - 2011-11-30 14:11:03
|
Hi Tim, Ok will do. I'll do that on Friday. Everyone, Last call for integrating your patch in 1.4 release. You'll have to wait another ~3yrs or so otherwise ;) Thanks ! On Wed, Nov 30, 2011 at 1:03 PM, Tim Hutton <tim...@gm...> wrote: > Hello, > > I've just been bitten by the fact that the 1.3 download (from 2008) is > older than some of the fixes in the CVS head. Specifically: the Timer > error has gone, and the Cocoa build wasn't working. I see there are > around 8 downloads a week so presumably all of these people are being > hit by these issues too! So please make a new download. > > And thankyou thankyou thankyou for maintaining wxVTK. I've been using > it continuously for several years now. > > -- > Tim Hutton - http://www.sq3.org.uk - http://profiles.google.com/tim.hutton/ > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure > contains a definitive record of customers, application performance, > security threats, fraudulent activity, and more. Splunk takes this > data and makes sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-novd2d > _______________________________________________ > Wxvtk-users mailing list > Wxv...@li... > https://lists.sourceforge.net/lists/listinfo/wxvtk-users > -- Mathieu |
|
From: Mathieu M. <mat...@gm...> - 2011-11-30 14:08:45
|
Hi Aris,
Give wxVTK from CVS a try and let us know if this works for you. Thanks.
HTH
On Wed, Nov 30, 2011 at 3:05 PM, Aris Basic <ari...@gm...> wrote:
> question about wxVTK
>
> are you still working on it ?
> in version that i downloaded (i think it is the latest one).
> samples are not really working (vtk errors about unable to create timer)
>
> i did quick fix for it by renaming CreateTimer into InternalCreateTimer
> which is not full fix (im guessing VTK does use multiple timers on occasion)
>
> so just checking on any updates before i potentially start to mess with it :)
>
> BTW here is what i have for InternalCreateTimer
>
> int wxVTKRenderWindowInteractor::InternalCreateTimer(int timerId, int
> timerType, unsigned long duration)
> {
> if (!timer.Start(duration,timerType == OneShotTimer))
> assert(false);
> return 1;
> }
>
--
Mathieu
|
|
From: Tim H. <tim...@gm...> - 2011-11-30 12:04:15
|
Hello, I've just been bitten by the fact that the 1.3 download (from 2008) is older than some of the fixes in the CVS head. Specifically: the Timer error has gone, and the Cocoa build wasn't working. I see there are around 8 downloads a week so presumably all of these people are being hit by these issues too! So please make a new download. And thankyou thankyou thankyou for maintaining wxVTK. I've been using it continuously for several years now. -- Tim Hutton - http://www.sq3.org.uk - http://profiles.google.com/tim.hutton/ |
|
From: Ruopeng W. <rp...@nm...> - 2010-07-15 21:16:03
|
Hi all, Just wondering if there is anyone successfully get wxVTK work on Snow Leopard (cocoa)? Also, how to get the latest CVS trunk? Thanks, Ruopeng The information in this e-mail is intended only for the person to whom it is addressed. If you believe this e-mail was sent to you in error and the e-mail contains patient information, please contact the Partners Compliance HelpLine at http://www.partners.org/complianceline . If the e-mail was sent to you in error but does not contain patient information, please contact the sender and properly dispose of the e-mail. |
|
From: Héber de P. S. <heb...@gm...> - 2010-07-14 22:21:38
|
Thanks for the help. It worked perfectly.
The wxvtk was not adjusted for the new versions of VTK even.
2010/7/13 ja...@be... <ja...@be...>
> Hello!
> I guess the program does not crash after issuing the error and by pressing
> t for
> trackball mode you can use the program. I was confronted with the same
> behaviour
> after upgrading from VTK 5.0 to VTK 5.6. My assumption is that the timer
> was
> changed and this timer is needed for joystick mode which is the default. If
> my
> assumptions are correct and after pressing t the window works as expected,
> you
> can add the lines between the clip and clap comments to the frame
> constructor:
>
> MyFrame::MyFrame( const wxString& title,
> const wxPoint& pos,
> const wxSize& size )
> : wxFrame((wxFrame *)NULL, -1, title, pos, size,
> wxDEFAULT_FRAME_STYLE |
> wxMAXIMIZE)
> {
> ...
> // ----- clip ------
> // We make use of trackball mode - joystick mode does not work
> vtkSmartPointer<vtkInteractorStyleSwitch> intStyle =
> vtkSmartPointer<vtkInteractorStyleSwitch>::New();
> intStyle->SetCurrentStyleToTrackballCamera();
>
> this->m_pVTKWindow = new wxVTKRenderWindowInteractor(this,
> MY_VTK_WINDOW);
> this->m_pVTKWindow->SetInteractorStyle(intStyle);
> this->m_pVTKWindow->UseCaptureMouseOn();
> // ----- clap ------
> ...
>
> Good luck!
> Reinhard
>
>
> "Héber de Padua Sousa" <heb...@gm...> hat am 10. Juli 2010 um
> 22:37 geschrieben:
>
> > hi, I need help.
> > I'm working in an aplication using vtk and wxvtk class.
> > In the sample wxSample occur a error while I drag the mouse. The
> interaction
> > not works.
> >
> > the log error is:
> > ERROR: In ..\..\Rendering\vtkInteractorStyle.cxx, line 392
> > vtkInteractorStyleJoystickCamera (0957E070): Timer start failed
> >
> > What can It is?
>
--
>> Héber de Padua Sousa
/~heber
|
|
From: <ja...@be...> - 2010-07-13 11:16:40
|
Hello!
I guess the program does not crash after issuing the error and by pressing t for
trackball mode you can use the program. I was confronted with the same behaviour
after upgrading from VTK 5.0 to VTK 5.6. My assumption is that the timer was
changed and this timer is needed for joystick mode which is the default. If my
assumptions are correct and after pressing t the window works as expected, you
can add the lines between the clip and clap comments to the frame constructor:
MyFrame::MyFrame( const wxString& title,
const wxPoint& pos,
const wxSize& size )
: wxFrame((wxFrame *)NULL, -1, title, pos, size, wxDEFAULT_FRAME_STYLE |
wxMAXIMIZE)
{
...
// ----- clip ------
// We make use of trackball mode - joystick mode does not work
vtkSmartPointer<vtkInteractorStyleSwitch> intStyle =
vtkSmartPointer<vtkInteractorStyleSwitch>::New();
intStyle->SetCurrentStyleToTrackballCamera();
this->m_pVTKWindow = new wxVTKRenderWindowInteractor(this, MY_VTK_WINDOW);
this->m_pVTKWindow->SetInteractorStyle(intStyle);
this->m_pVTKWindow->UseCaptureMouseOn();
// ----- clap ------
...
Good luck!
Reinhard
"Héber de Padua Sousa" <heb...@gm...> hat am 10. Juli 2010 um 22:37
geschrieben:
> hi, I need help.
> I'm working in an aplication using vtk and wxvtk class.
> In the sample wxSample occur a error while I drag the mouse. The interaction
> not works.
>
> the log error is:
> ERROR: In ..\..\Rendering\vtkInteractorStyle.cxx, line 392
> vtkInteractorStyleJoystickCamera (0957E070): Timer start failed
>
> What can It is? |
|
From: Héber de P. S. <heb...@gm...> - 2010-07-10 20:38:00
|
hi, I need help. I'm working in an aplication using vtk and wxvtk class. In the sample wxSample occur a error while I drag the mouse. The interaction not works. the log error is: ERROR: In ..\..\Rendering\vtkInteractorStyle.cxx, line 392 vtkInteractorStyleJoystickCamera (0957E070): Timer start failed What can It is? |
|
From: Rupert B. <rup...@gm...> - 2010-04-06 11:29:57
|
Hi, Yes, its libgtk2, which i had the dev installed. Ultimately i had to install the following packages (most were already installed, but not in the include path) and set my CPATH as follows for it to work libgtk2.0-dev libglib2.0-dev libpango1.0-dev libcairo2-dev libatk1.0-dev libatk1.0-dev export CPATH=/usr/include/gtk-2.0:/usr/include/glib-2.0:/usr/lib/glib-2.0/include:/usr/include/pango-1.0:/usr/include/cairo:/usr/lib/gtk-2.0/include:/usr/include/atk-1.0 Sadly, even once built, it seems not to work properly. Clicking in the window gives the following errors rupert@morrigan:~/development/wxVTK/wxVTK-build$ bin/wxSample ERROR: In /build/buildd/vtk-5.2.1/Rendering/vtkInteractorStyle.cxx, line 392 vtkInteractorStyleJoystickCamera (0x17ee510): Timer start failed ERROR: In /build/buildd/vtk-5.2.1/Rendering/vtkInteractorStyle.cxx, line 392 vtkInteractorStyleJoystickCamera (0x17ee510): Timer start failed ERROR: In /build/buildd/vtk-5.2.1/Rendering/vtkInteractorStyle.cxx, line 392 vtkInteractorStyleJoystickCamera (0x17ee510): Timer start failed I've found another solution to what i wanted to do so I'm going to stop following this path. But I just wanted to let you know that on Ubuntu Karmic, 64-bit, it seems to give quite a bit of trouble. The vtk that im using is the Ubuntu vtk (5.2). Cheers Rupert -------------------------------------------------------------- Rupert Brooks rup...@gm... On Tue, Apr 6, 2010 at 04:01, Mathieu Malaterre <mat...@gm...> wrote: > Rupert, > > On Mon, Apr 5, 2010 at 2:41 PM, Rupert Brooks <rup...@gm...> wrote: >> I downloaded wxVTK and tried to build and install, but ran into the >> following compilation error. The same error occurs whether i have >> wx2.6 installed or wx2.8 >> >> rupert@morrigan:~/development/wxVTK/wxVTK-build$ make >> [ 10%] Building CXX object >> CMakeFiles/wxImagePlaneWidget.dir/Sample/wxImagePlaneWidget.cxx.o >> [ 20%] Building CXX object >> CMakeFiles/wxImagePlaneWidget.dir/src/wxVTKRenderWindowInteractor.cxx.o >> /home/rupert/development/wxVTK/wxVTK/src/wxVTKRenderWindowInteractor.cxx:61:81: >> error: gdk/gdkx.h: No such file or directory >> /home/rupert/development/wxVTK/wxVTK/src/wxVTKRenderWindowInteractor.cxx:62:32: >> error: gdk/gdkprivate.h: No such file or directory > > In order to get the X11 pointer wxVTK access the wxVTK window pointer, > then the gdk handle and underneath the X11 window. So you *need* the > gdk dev package. Whichever package that provide 'gdk/gdkprivate.h', > pick the one associated with your wx version. > > > HTH > -- > Mathieu > |
|
From: Mathieu M. <mat...@gm...> - 2010-04-06 08:02:17
|
Rupert, On Mon, Apr 5, 2010 at 2:41 PM, Rupert Brooks <rup...@gm...> wrote: > I downloaded wxVTK and tried to build and install, but ran into the > following compilation error. The same error occurs whether i have > wx2.6 installed or wx2.8 > > rupert@morrigan:~/development/wxVTK/wxVTK-build$ make > [ 10%] Building CXX object > CMakeFiles/wxImagePlaneWidget.dir/Sample/wxImagePlaneWidget.cxx.o > [ 20%] Building CXX object > CMakeFiles/wxImagePlaneWidget.dir/src/wxVTKRenderWindowInteractor.cxx.o > /home/rupert/development/wxVTK/wxVTK/src/wxVTKRenderWindowInteractor.cxx:61:81: > error: gdk/gdkx.h: No such file or directory > /home/rupert/development/wxVTK/wxVTK/src/wxVTKRenderWindowInteractor.cxx:62:32: > error: gdk/gdkprivate.h: No such file or directory In order to get the X11 pointer wxVTK access the wxVTK window pointer, then the gdk handle and underneath the X11 window. So you *need* the gdk dev package. Whichever package that provide 'gdk/gdkprivate.h', pick the one associated with your wx version. HTH -- Mathieu |
|
From: Rupert B. <rup...@gm...> - 2010-04-05 12:41:28
|
Hi,
I downloaded wxVTK and tried to build and install, but ran into the
following compilation error. The same error occurs whether i have
wx2.6 installed or wx2.8
rupert@morrigan:~/development/wxVTK/wxVTK-build$ make
[ 10%] Building CXX object
CMakeFiles/wxImagePlaneWidget.dir/Sample/wxImagePlaneWidget.cxx.o
[ 20%] Building CXX object
CMakeFiles/wxImagePlaneWidget.dir/src/wxVTKRenderWindowInteractor.cxx.o
/home/rupert/development/wxVTK/wxVTK/src/wxVTKRenderWindowInteractor.cxx:61:81:
error: gdk/gdkx.h: No such file or directory
/home/rupert/development/wxVTK/wxVTK/src/wxVTKRenderWindowInteractor.cxx:62:32:
error: gdk/gdkprivate.h: No such file or directory
In file included from
/home/rupert/development/wxVTK/wxVTK/src/wxVTKRenderWindowInteractor.cxx:70:
/usr/include/wx-2.6/wx/gtk/win_gtk.h:18:21: error: gdk/gdk.h: No such
file or directory
/usr/include/wx-2.6/wx/gtk/win_gtk.h:20:30: error: gtk/gtkcontainer.h:
No such file or directory
/usr/include/wx-2.6/wx/gtk/win_gtk.h:21:31: error:
gtk/gtkadjustment.h: No such file or directory
In file included from
/home/rupert/development/wxVTK/wxVTK/src/wxVTKRenderWindowInteractor.cxx:70:
/usr/include/wx-2.6/wx/gtk/win_gtk.h:56: error: ‘GtkContainer’ does
not name a type
/usr/include/wx-2.6/wx/gtk/win_gtk.h:57: error: expected ‘;’ before ‘*’ token
/usr/include/wx-2.6/wx/gtk/win_gtk.h:68: error: ‘GdkVisibilityState’
does not name a type
/usr/include/wx-2.6/wx/gtk/win_gtk.h:73: error: ‘gboolean’ does not name a type
/usr/include/wx-2.6/wx/gtk/win_gtk.h:74: error: ‘gboolean’ does not name a type
/usr/include/wx-2.6/wx/gtk/win_gtk.h:75: error: ‘gboolean’ does not name a type
/usr/include/wx-2.6/wx/gtk/win_gtk.h:80: error: ‘GtkContainerClass’
does not name a type
/usr/include/wx-2.6/wx/gtk/win_gtk.h:88: error: ‘GtkType’ does not name a type
/usr/include/wx-2.6/wx/gtk/win_gtk.h:98: error: ‘gboolean’ has not been declared
/usr/include/wx-2.6/wx/gtk/win_gtk.h:102: error: ‘gboolean’ has not
been declared
/usr/include/wx-2.6/wx/gtk/win_gtk.h:106: error: ‘gboolean’ has not
been declared
/home/rupert/development/wxVTK/wxVTK/src/wxVTKRenderWindowInteractor.cxx:
In member function ‘long int
wxVTKRenderWindowInteractor::GetHandleHack()’:
/home/rupert/development/wxVTK/wxVTK/src/wxVTKRenderWindowInteractor.cxx:344:
error: ‘gtk_pizza_get_type’ was not declared in this scope
/home/rupert/development/wxVTK/wxVTK/src/wxVTKRenderWindowInteractor.cxx:344:
error: expected primary-expression before ‘)’ token
/home/rupert/development/wxVTK/wxVTK/src/wxVTKRenderWindowInteractor.cxx:344:
error: ‘GTK_CHECK_CAST’ was not declared in this scope
/home/rupert/development/wxVTK/wxVTK/src/wxVTKRenderWindowInteractor.cxx:344:
error: ‘GDK_WINDOW_XWINDOW’ was not declared in this scope
/home/rupert/development/wxVTK/wxVTK/src/wxVTKRenderWindowInteractor.cxx:344:
error: invalid use of incomplete type ‘struct _GtkWidget’
/usr/include/wx-2.6/wx/defs.h:2777: error: forward declaration of
‘struct _GtkWidget’
make[2]: *** [CMakeFiles/wxImagePlaneWidget.dir/src/wxVTKRenderWindowInteractor.cxx.o]
Error 1
make[1]: *** [CMakeFiles/wxImagePlaneWidget.dir/all] Error 2
I tried putting the gtk2.0 includes in my include path, and it got a
bit farther, but then ran into more problems
rupert@morrigan:~/development/wxVTK/wxVTK-build$ export
CPATH=/usr/include/gtk-2.0
rupert@morrigan:~/development/wxVTK/wxVTK-build$ make
[ 10%] Building CXX object
CMakeFiles/wxImagePlaneWidget.dir/src/wxVTKRenderWindowInteractor.cxx.o
In file included from /usr/include/gtk-2.0/gdk/gdk.h:32,
from /usr/include/gtk-2.0/gdk/gdkprivate.h:30,
from /usr/include/gtk-2.0/gdk/gdkx.h:30,
from
/home/rupert/development/wxVTK/wxVTK/src/wxVTKRenderWindowInteractor.cxx:61:
/usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30:21: error:
gio/gio.h: No such file or directory
In file included from
/usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:31,
from /usr/include/gtk-2.0/gdk/gdk.h:32,
from /usr/include/gtk-2.0/gdk/gdkprivate.h:30,
from /usr/include/gtk-2.0/gdk/gdkx.h:30,
from
/home/rupert/development/wxVTK/wxVTK/src/wxVTKRenderWindowInteractor.cxx:61:
[...snipped...]
Do you have any tips for compilation on ubuntu karmic?
Thanks
Rupert B
--------------------------------------------------------------
Rupert Brooks
rup...@gm...
|
|
From: Thiago F. M. <tot...@gm...> - 2010-02-23 14:00:07
|
On Tue, Feb 23, 2010 at 5:56 AM, Mathieu Malaterre <
mat...@gm...> wrote:
> On Tue, Feb 23, 2010 at 12:11 AM, Thiago Franco de Moraes
> <tot...@gm...> wrote:
> > On 22-02-2010 18:51, Mathieu Malaterre wrote:
> >> Works for me here.
> >>
> >> What is the backtrace ?
> >
> > There is only a segmentation fault. I forgot to said that error occurs
> > using Python. I tried in Window too, and it works.
>
> The Python version is maintained directly in VTK. You should try the
> vtk users mailing list.
>
I have already posted there. I'll post this message there too
> BTW you can still catch those signal from python:
>
> gdb python myscript.py
> > run
>
> HTH
> --
> Mathieu
>
I tried that command and it doesn't work. Then I tried this ways:
$ gdb python
Then:
(gdb) run wxVTKRenderWindowInteractor.py
It give me this message:
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff100f840 in XChangeWindowAttributes () from /usr/lib/libX11.so.6
So I run this command:
(gdb) backtrace full
#0 0x00007ffff100f840 in XChangeWindowAttributes () from
/usr/lib/libX11.so.6
No symbol table info available.
#1 0x00007fffe60a19de in vtkXOpenGLRenderWindow::CreateAWindow
(this=0x185f310) at
/home/tfmoraes/Download/vtkcvs/VTK/Rendering/vtkXOpenGLRenderWindow.cxx:588
matcher = {visual = 0x94d057, visualid = 4294967295, screen = -1,
depth = 0, c_class = -150812852, red_mask = 25685472, green_mask =
140737158771210,
blue_mask = 140737488340640, colormap_size = 1, bits_per_rgb = 0}
width = 400
height = 400
xsh = {flags = 3, x = 0, y = 0, width = 400, height = 400, min_width
= 8904864, min_height = 0, max_width = 9752663, max_height = 0, width_inc =
-1,
height_inc = 0, min_aspect = {x = -1, y = 0}, max_aspect = {x =
-147730880, y = 32767}, base_width = -14976, base_height = 32767,
win_gravity = 8904864}
attr = {background_pixmap = 9752663, background_pixel = 4294967295,
border_pixmap = 4294967295, border_pixel = 140737340624448, bit_gravity =
-15120,
win_gravity = 32767, backing_store = 8904864, backing_planes =
9752663, backing_pixel = 4294967295, save_under = -1, event_mask =
140737340624448,
do_not_propagate_mask = 140737488340256, override_redirect = 0,
colormap = 9752663, cursor = 4294967295}
x = 0
winattr = {x = -15296, y = 32767, width = -147730880, height =
32767, border_width = 48, depth = 0, visual = 0x7ffff731ce40, root =
140737488340064,
c_class = 8904864, bit_gravity = 0, win_gravity = 9752663,
backing_store = 0, backing_planes = 4294967295, backing_pixel = 4294967295,
save_under = -147730880, colormap = 140737488340112, map_installed
= 8904864, map_state = 0, all_event_masks = 9752663, your_event_mask =
4294967295,
do_not_propagate_mask = 4294967295, override_redirect =
-147730880, screen = 0x7fffffffc4c0}
v = 0x187edc0
y = 0
nItems = -14688
#2 0x00007fffe60a3191 in vtkXOpenGLRenderWindow::WindowInitialize
(this=0x185f310) at
/home/tfmoraes/Download/vtkcvs/VTK/Rendering/vtkXOpenGLRenderWindow.cxx:1031
ren = 0x7fffffffc6a0
#3 0x00007fffe60a3265 in vtkXOpenGLRenderWindow::Initialize
(this=0x185f310) at
/home/tfmoraes/Download/vtkcvs/VTK/Rendering/vtkXOpenGLRenderWindow.cxx:1053
No locals.
#4 0x00007fffe60a3701 in vtkXOpenGLRenderWindow::Start (this=0x185f310) at
/home/tfmoraes/Download/vtkcvs/VTK/Rendering/vtkXOpenGLRenderWindow.cxx:1186
No locals.
#5 0x00007fffe5f6dc35 in vtkRenderWindow::DoStereoRender (this=0x185f310)
at /home/tfmoraes/Download/vtkcvs/VTK/Rendering/vtkRenderWindow.cxx:688
rsit = 0xffffc701
#6 0x00007fffe5f6dc06 in vtkRenderWindow::DoFDRender (this=0x185f310) at
/home/tfmoraes/Download/vtkcvs/VTK/Rendering/vtkRenderWindow.cxx:677
i = 32767
#7 0x00007fffe5f6d6bd in vtkRenderWindow::DoAARender (this=0x185f310) at
/home/tfmoraes/Download/vtkcvs/VTK/Rendering/vtkRenderWindow.cxx:564
i = 32767
#8 0x00007fffe5f6cc93 in vtkRenderWindow::Render (this=0x185f310) at
/home/tfmoraes/Download/vtkcvs/VTK/Rendering/vtkRenderWindow.cxx:377
size = 0x185f380
x = 1155115008
y = 0
p1 = 0x1873638
#9 0x00007fffe60a5ed1 in vtkXOpenGLRenderWindow::Render (this=0x185f310) at
/home/tfmoraes/Download/vtkcvs/VTK/Rendering/vtkXOpenGLRenderWindow.cxx:1846
attribs = {x = -13968, y = 32767, width = -323898245, height =
32767, border_width = 0, depth = 0, visual = 0x185f310, root = 20467688,
c_class = -438120533, bit_gravity = 32767, win_gravity = 25638456,
backing_store = 0, backing_planes = 25443968, backing_pixel = 22463728,
save_under = 21494544, colormap = 20467624, map_installed =
-151501984, map_state = 32767, all_event_masks = 0, your_event_mask =
4678969,
do_not_propagate_mask = 23140944, override_redirect = -134709168,
screen = 0x7ffff7f88050}
#10 0x00007fffe671d370 in PyvtkXOpenGLRenderWindow_Render (self=0x1611a50,
args=0x7ffff7f88050)
at
/home/tfmoraes/Download/vtkcvs/VTK/Rendering/vtkXOpenGLRenderWindowPython.cxx:1166
op = 0x185f310
#11 0x00000000004a290d in PyEval_EvalFrameEx ()
No symbol table info available.
#12 0x00000000004a2e47 in PyEval_EvalFrameEx ()
---Type <return> to continue, or q <return> to quit---
No symbol table info available.
#13 0x00000000004a40e0 in PyEval_EvalCodeEx ()
No symbol table info available.
#14 0x000000000052be30 in ?? ()
No symbol table info available.
#15 0x000000000041d6e7 in PyObject_Call ()
No symbol table info available.
#16 0x00000000004254ff in ?? ()
No symbol table info available.
#17 0x000000000041d6e7 in PyObject_Call ()
No symbol table info available.
#18 0x000000000049c623 in PyEval_CallObjectWithKeywords ()
No symbol table info available.
#19 0x00007ffff6b71b17 in wxPyCallback::EventThunker(wxEvent&) () from
/usr/lib/python2.6/dist-packages/wx-2.8-gtk2-unicode/wx/_core_.so
No symbol table info available.
#20 0x00007ffff4e9ef89 in
wxEvtHandler::ProcessEventIfMatches(wxEventTableEntryBase const&,
wxEvtHandler*, wxEvent&) () from /usr/lib/libwx_baseu-2.8.so.0
No symbol table info available.
#21 0x00007ffff4e9f134 in wxEvtHandler::SearchDynamicEventTable(wxEvent&) ()
from /usr/lib/libwx_baseu-2.8.so.0
No symbol table info available.
#22 0x00007ffff4ea0222 in wxEvtHandler::ProcessEvent(wxEvent&) () from
/usr/lib/libwx_baseu-2.8.so.0
No symbol table info available.
#23 0x00007fffdf22f572 in wxGLCanvas::OnInternalIdle() () from
/usr/lib/libwx_gtk2u_gl-2.8.so.0
No symbol table info available.
#24 0x00007ffff57b3ded in wxAppBase::SendIdleEvents(wxWindow*, wxIdleEvent&)
() from /usr/lib/libwx_gtk2u_core-2.8.so.0
No symbol table info available.
#25 0x00007ffff57b3e24 in wxAppBase::SendIdleEvents(wxWindow*, wxIdleEvent&)
() from /usr/lib/libwx_gtk2u_core-2.8.so.0
No symbol table info available.
#26 0x00007ffff57b4084 in wxAppBase::ProcessIdle() () from
/usr/lib/libwx_gtk2u_core-2.8.so.0
No symbol table info available.
#27 0x00007ffff5716954 in ?? () from /usr/lib/libwx_gtk2u_core-2.8.so.0
No symbol table info available.
#28 0x00007ffff24e2bce in g_main_context_dispatch () from
/lib/libglib-2.0.so.0
No symbol table info available.
#29 0x00007ffff24e6598 in ?? () from /lib/libglib-2.0.so.0
No symbol table info available.
#30 0x00007ffff24e69f5 in g_main_loop_run () from /lib/libglib-2.0.so.0
No symbol table info available.
#31 0x00007ffff43bc177 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
No symbol table info available.
#32 0x00007ffff572df58 in wxEventLoop::Run() () from
/usr/lib/libwx_gtk2u_core-2.8.so.0
No symbol table info available.
#33 0x00007ffff57b3ebb in wxAppBase::MainLoop() () from
/usr/lib/libwx_gtk2u_core-2.8.so.0
No symbol table info available.
#34 0x00007ffff6b6fdd7 in wxPyApp::MainLoop() () from
/usr/lib/python2.6/dist-packages/wx-2.8-gtk2-unicode/wx/_core_.so
No symbol table info available.
#35 0x00007ffff6be57de in ?? () from
/usr/lib/python2.6/dist-packages/wx-2.8-gtk2-unicode/wx/_core_.so
No symbol table info available.
#36 0x00000000004a2299 in PyEval_EvalFrameEx ()
---Type <return> to continue, or q <return> to quit---
No symbol table info available.
#37 0x00000000004a40e0 in PyEval_EvalCodeEx ()
No symbol table info available.
#38 0x000000000052be30 in ?? ()
No symbol table info available.
#39 0x000000000041d6e7 in PyObject_Call ()
No symbol table info available.
#40 0x00000000004254ff in ?? ()
No symbol table info available.
#41 0x000000000041d6e7 in PyObject_Call ()
No symbol table info available.
#42 0x00000000004a199c in PyEval_EvalFrameEx ()
No symbol table info available.
#43 0x00000000004a2e47 in PyEval_EvalFrameEx ()
No symbol table info available.
#44 0x00000000004a2e47 in PyEval_EvalFrameEx ()
No symbol table info available.
#45 0x00000000004a40e0 in PyEval_EvalCodeEx ()
No symbol table info available.
#46 0x00000000004a41b2 in PyEval_EvalCode ()
No symbol table info available.
#47 0x00000000004c33a0 in PyRun_FileExFlags ()
No symbol table info available.
#48 0x00000000004c3564 in PyRun_SimpleFileExFlags ()
No symbol table info available.
#49 0x0000000000418ab7 in Py_Main ()
No symbol table info available.
#50 0x00007ffff6fd0abd in __libc_start_main () from /lib/libc.so.6
No symbol table info available.
#51 0x0000000000417ca9 in _start ()
No symbol table info available.
|
|
From: Mathieu M. <mat...@gm...> - 2010-02-23 08:57:20
|
On Tue, Feb 23, 2010 at 12:11 AM, Thiago Franco de Moraes <tot...@gm...> wrote: > On 22-02-2010 18:51, Mathieu Malaterre wrote: >> Works for me here. >> >> What is the backtrace ? > > There is only a segmentation fault. I forgot to said that error occurs > using Python. I tried in Window too, and it works. The Python version is maintained directly in VTK. You should try the vtk users mailing list. BTW you can still catch those signal from python: gdb python myscript.py > run HTH -- Mathieu |
|
From: Thiago F. de M. <tot...@gm...> - 2010-02-22 23:11:51
|
On 22-02-2010 18:51, Mathieu Malaterre wrote: > Works for me here. > > What is the backtrace ? There is only a segmentation fault. I forgot to said that error occurs using Python. I tried in Window too, and it works. > On Mon, Feb 22, 2010 at 8:46 PM, Thiago Franco Moraes > <tot...@gm...> wrote: >> Hi, >> >> Whenever a Render is called the wxVTKRenderWindowInteractor crashes with a >> segmentation fault I've been using cvs vtk version. In the last revision the >> wxVTKRenderWindowInteractor doesn't work, the wxVTKRenderWindow works. I >> tried in Fedora 12 32 bits, Ubuntu 9.10 64 bits and Ubuntu 9.04 32 bits. The >> vtk has been installed in a virtualenv environment. I generated a core dump >> from this error, if necessary I can send. >> >> Thanks! >> >> ------------------------------------------------------------------------------ >> Download Intel® Parallel Studio Eval >> Try the new software tools for yourself. Speed compiling, find bugs >> proactively, and fine-tune applications for parallel performance. >> See why Intel Parallel Studio got high marks during beta. >> http://p.sf.net/sfu/intel-sw-dev >> _______________________________________________ >> Wxvtk-users mailing list >> Wxv...@li... >> https://lists.sourceforge.net/lists/listinfo/wxvtk-users >> >> > > > |
|
From: Mathieu M. <mat...@gm...> - 2010-02-22 21:52:11
|
Works for me here. What is the backtrace ? On Mon, Feb 22, 2010 at 8:46 PM, Thiago Franco Moraes <tot...@gm...> wrote: > Hi, > > Whenever a Render is called the wxVTKRenderWindowInteractor crashes with a > segmentation fault I've been using cvs vtk version. In the last revision the > wxVTKRenderWindowInteractor doesn't work, the wxVTKRenderWindow works. I > tried in Fedora 12 32 bits, Ubuntu 9.10 64 bits and Ubuntu 9.04 32 bits. The > vtk has been installed in a virtualenv environment. I generated a core dump > from this error, if necessary I can send. > > Thanks! > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Wxvtk-users mailing list > Wxv...@li... > https://lists.sourceforge.net/lists/listinfo/wxvtk-users > > -- Mathieu |
|
From: Thiago F. M. <tot...@gm...> - 2010-02-22 19:46:16
|
Hi, Whenever a Render is called the wxVTKRenderWindowInteractor crashes with a segmentation fault I've been using cvs vtk version. In the last revision the wxVTKRenderWindowInteractor doesn't work, the wxVTKRenderWindow works. I tried in Fedora 12 32 bits, Ubuntu 9.10 64 bits and Ubuntu 9.04 32 bits. The vtk has been installed in a virtualenv environment. I generated a core dump from this error, if necessary I can send. Thanks! |
|
From: Kenneth P. <sh...@se...> - 2010-01-02 08:54:06
|
See this bug: <https://sourceforge.net/tracker/?func=detail&aid=1704344&group_id=114757&atid=669338> The problem is that under Win32, the interactor class is derived from a stub base class, not the Win32 subclass that provides a timer implementation. I suspect I'll see a similar problem when I build for Linux, as it probably should be based on the X subclass. I'm working on a patch. With the correct interactor base class, I'm now seeing a wx warning that wxMouseCaptureLostEvent is not being handled. |
|
From: Thiago F. M. <tfm...@ct...> - 2009-11-23 15:20:57
|
Hi, There is a way to Bind EVT_PAINT in the wxVTKRenderwindowInteractor and to draw above it without the wxVTKRenderwindowInteractor stuff delete what I drawed? Thanks! PS. Sorry for the repeated message, a error occurred here. |
|
From: Thiago F. M. <tot...@gm...> - 2009-11-23 15:18:58
|
Hi, There is a way to Bind EVT_PAINT in the wxVTKRenderwindowInteractor and to draw above it without the wxVTKRenderwindowInteractor stuff delete what I drawed? Thanks! |
|
From: Thiago F. M. <tot...@gm...> - 2009-11-23 15:17:01
|
Hi, There is a way to Bind EVT_PAINT in the wxVTKRenderwindowInteractor and to draw above it without the wxVTKRenderwindowInteractor stuff delete what I drawed? Thanks! |
|
From: Thiago F. M. <tfm...@ct...> - 2009-11-23 15:07:50
|
Hi, There is a way to Bind EVT_PAINT in the wxVTKRenderwindowInteractor and to draw above it without the wxVTKRenderwindowInteractor stuff delete what I drawed? Thanks! |
|
From: Thiago F. M. <tot...@gm...> - 2009-11-23 15:06:56
|
Hi, There is a way to Bind EVT_PAINT in the wxVTKRenderwindowInteractor and to draw above it without the wxVTKRenderwindowInteractor stuff delete what I drawed? Thanks! |
|
From: Mathieu M. <mat...@gm...> - 2009-10-23 10:42:19
|
You need to use the same RenderWindow, this is the trick.
On Fri, Oct 16, 2009 at 5:57 PM, Suyang Mei <suy...@ya...> wrote:
>
> Hi, all -
>
> I am new to wxVTK even VTK world.
>
> I need to implement a 2D slicer to display 2D slices from a 3D volume by using wxWidget, python & VTK. By searching the web, I am planning to use vtkImageViewer2 to implement it, is this a good choice? any suggestion?
>
> Here is the sample codes I am working on (I use a 2D slice to start with, the Forest4.png with the size of 192 & 256) -
>
> ####################################
> import vtk
> from vtk.util.misc import vtkGetDataRoot
> from vtk.wx.wxVTKRenderWindowInteractor import *
> from wxPython.wx import *
>
> app = wxPySimpleApp()
>
> frame = wxFrame(None, -1, "wxRenderWindow", size=wxSize(400,400))
> frame.Show(1)
>
> reader = vtk.vtkPNGReader ()
> reader.SetDataSpacing (1.0, 1.0, 1.0)
> reader.SetFileName ( "Forest4.png")
>
> iren = wxVTKRenderWindowInteractor(frame, -1)
> iren.AddObserver("ExitEvent", lambda o,e,f=frame: f.Close())
>
> viewer = vtk.vtkImageViewer2()
> viewer.SetInput ( reader.GetOutput() )
> viewer.SetupInteractor (iren)
> #viewer.GetRenderer().ResetCameraClippingRange()
>
> app.MainLoop()
> ####################################
>
> When I run this *.py file, I got the image displayed at the upper left corner of the view port, only occupied a small portion. How do I correctly set the zoom factor?
>
> I googled vtkImageViewer2, back to 2003, there were many posts about bugs inside vtkImageViewer2 when using wxWidget -
>
> http://public.kitware.com/pipermail/vtkusers/2003-September/069419.html
>
> Is this problem fixed? I am using VTK version 5.2, wxPython 2.8.9.1, and I am in linux.
>
> Any suggestions will be helpful, thanks.
>
> Suyang
>
>
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Wxvtk-users mailing list
> Wxv...@li...
> https://lists.sourceforge.net/lists/listinfo/wxvtk-users
>
--
Mathieu
|
|
From: Suyang M. <suy...@ya...> - 2009-10-16 15:57:23
|
Hi, all -
I am new to wxVTK even VTK world.
I
need to implement a 2D slicer to display 2D slices from a 3D volume by
using wxWidget, python & VTK. By searching the web, I am planning
to use vtkImageViewer2 to implement it, is this a good choice? any
suggestion?
Here is the sample codes I am
working on (I use a 2D slice to start with, the Forest4.png with the
size of 192 & 256) -
####################################
import vtk
from vtk.util.misc import vtkGetDataRoot
from vtk.wx.wxVTKRenderWindowInteractor import *
from wxPython.wx import *
app = wxPySimpleApp()
frame = wxFrame(None, -1, "wxRenderWindow", size=wxSize(400,400))
frame.Show(1)
reader = vtk.vtkPNGReader ()
reader.SetDataSpacing (1.0, 1.0,
1.0)
reader.SetFileName ( "Forest4.png")
iren = wxVTKRenderWindowInteractor(frame, -1)
iren.AddObserver("ExitEvent", lambda o,e,f=frame: f.Close())
viewer = vtk.vtkImageViewer2()
viewer.SetInput ( reader.GetOutput() )
viewer.SetupInteractor (iren)
#viewer.GetRenderer().ResetCameraClippingRange()
app.MainLoop()
####################################
When I run this *.py file, I got the image displayed at the upper left
corner of the view port, only occupied a small portion. How do I
correctly set the zoom factor?
I googled vtkImageViewer2, back to 2003, there were many posts about bugs inside vtkImageViewer2 when using wxWidget -
http://public.kitware.com/pipermail/vtkusers/2003-September/069419.html
Is this problem fixed? I am using VTK version 5.2, wxPython 2.8.9.1, and I am in linux.
Any suggestions will be helpful, thanks.
Suyang
|
4 messages has been excluded from this view by a project administrator.
