Just a quick clarification Marcus meant ParaView 3.12 not ParaView 4.12.<br><br><div class="gmail_quote">On Fri, Jun 3, 2011 at 10:38 AM, Marcus D. Hanwell <span dir="ltr"><<a href="mailto:marcus.hanwell@kitware.com" target="_blank">marcus.hanwell@kitware.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>On Fri, Jun 3, 2011 at 3:19 AM, <<a href="mailto:owen.arnold@stfc.ac.uk" target="_blank">owen.arnold@stfc.ac.uk</a>> wrote:<br>
> Hi,<br>
><br>
> I was wondering if there are any plans to update the version of Qt against<br>
> which Paraview is built? I believe Qt 4.6 is currently being used with<br>
> Paraview 3.10.1. Are there any plans to upgrade to Qt 4.7 in future<br>
> releases?<br>
><br>
</div>Hi,<br>
<br>
Qt 4.6 is the officially supported Qt version for the 3.10 release,<br>
but I was testing and developing with Qt 4.7 for a large part of its<br>
development cycle. I was also submitting nightly dashboards for<br>
ParaView and VTK, so if you would like a more recent version of Qt for<br>
some reason there should not be any issues in recompiling against Qt<br>
4.7. Most testing effort focused on Qt 4.6 though, and that will<br>
remain the officially supported version for ParaView 3.10.<br>
<br>
Is there a particular feature you need from Qt 4.7 in ParaView? I<br>
think 4.12 will be moved to Qt 4.7 (or perhaps 4.8 depending on<br>
timing).<br>
<br>
Marcus<br>
_______________________________________________<br>
Paraview-developers mailing list<br>
<a href="mailto:Paraview-developers@paraview.org" target="_blank">Paraview-developers@paraview.org</a><br>
<a href="http://public.kitware.com/mailman/listinfo/paraview-developers" target="_blank">http://public.kitware.com/mailman/listinfo/paraview-developers</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Robert Maynard<br>