[vtkusers] The real difference between QVTKWidget and QVTKWidget2
Michael Jackson
mike.jackson at bluequartz.net
Fri Apr 29 14:44:00 EDT 2016
We are also getting a similar issue on OS X? Has anyone else seen this
problem? Is QVtkWidget2 ready for use or does it need more development
time on OS X?
Thanks
--
Mike Jackson [mike.jackson at bluequartz.net]
on March 10 2016 Thales Luis Rodrigues Sabino wrote:
> I'm building an application that uses VTK for visualization.
> My initial intent was to process large volumes of data.
> My application is being built with Qt + VTK.
>
> When I started coding the visualization toolkit with VTK I found the
> *QVTKWidget*. So far so good, I found another one, called
> *QVTKWidget2*. In
> the *QVTKWidget2*.h header there is the following statement:
>
> *// .NAME QVTKWidget2 - Display a vtkRenderWindow in a Qt's QGLWidget.*
> *// .SECTION Description*
> *// QVTKWidget2 provides a way to display VTK data in a Qt OpenGL widget.*
>
> Well, since this class uses the *QGLWidget* (which BTW is now deprecated,
> replaced by *QOpenGLWidget*), I decided to use this one. I also based my
> decision in some discussion I read about *QVTKWidget2* being a future
> replacement for the *QVTKWidget* class.
>
> Everything was fine until I decided to run my application on MacOS and the
> QVTKWidget2 object was crashing in initialization.
>
> I then replaced my widget to one of *QVTKWidget* and everything is now
> working fine (at least in the initial tests).
>
> So, with this context, my question is, do I get any advantage by using
> *QVTKWidget2*?
>
> My first thought was *'yes'*, since the *QVTKWidget* is a subclass of
> *QWidget*.
>
> Hope someone could clarify this for me.
>
> --
> Thales Luis Rodrigues Sabino
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtkusers/attachments/20160429/ee86bd90/attachment.html>
More information about the vtkusers
mailing list