[vtk-developers] VTK and QT5

[Utkarsh Ayachit]

+1.

One little caveat, I have only added support for the new
QVTKOpenGLWidget for OpenGL2 backend. While it may be possible to use
it with OpenGL1 backend it will need more testing and debugging. There
was a lot of rendering code that made assumptions about active frame
buffer that didn't work with QVTKOpenGLWidget that needed fixing. I
don't think this should be a hurdle in moving to Qt 5, but thought I'd
mention.

So far, the QVTKOpenGLWidget has been working well for ParaView. We
got Windows and Linux dashboards clean and green. We'll soon be adding
OsX dashboards too (need some unrelated fixes before that can happen).

Utkarsh

On Thu, Jan 19, 2017 at 9:43 AM, Marcus D. Hanwell
<marcus.hanwell at kitware.com> wrote:
> On Thu, Jan 19, 2017 at 12:20 AM, Andrew Maclean
> <andrew.amaclean at gmail.com> wrote:
>> I see that on the ParaView Developers list that they are moving to Qt5 by
>> default. See Utkarsh's post on Mon 16 Jan 2017, titled: "ParaView and Qt 5".
>>
>> Given that ParaView is built on VTK and that Qt5 is well supported on modern
>> machines. Isn't it time that VTK defaulted to Qt5 also?
>>
>> It seems to me that is a good opportunity to do this now that VTK has moved
>> to C++11.
>>
> I totally agree, and have been wanting to move VTK forward for a
> while. One of the big blockers was the QVTKWidget (and its sequel),
> but the new QVTKOpenGLWidget fixes those issues. We are looking for
> any remaining issues, and I think need to require at least Qt 5.5 for
> some fixes to the way events are squashed (need to check as my memory
> is hazy on what release they got in).
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>
> Search the list archives at: http://markmail.org/search/?q=vtk-developers
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/vtk-developers
>