Claire,
To launch ParaView that I build on Windows, I had to explicitly add the QT
bin directory to my path, for example C:/Qt/Qt5.8.0/5.8/msvc2015_64/bin
I'm not sure QT has provided binaries for the latest VisualStudio, have
they? I'm using VS2015, which is VS 14.0, I believe. You may have to
That definitely makes me think it was due to compatibility between the
compiler used for QT and the compiler used for ParaView - they need to be
the same. I'm surprised you got ParaView to link with the newer version of
VisualStudio - there may be a way to make that work which is eluding us.
Glad
I can confirm that the bug still exists on Windows with the ParaView 5.4.1
binaries downloaded from paraview.org.
To fix it, you can do a little patch to your installation of ParaView.
In the file
{ParaViewInstallDir}\bin\Lib\site-packages\paraview\web\protocols.py,
around line 1070, add these
Hi Eduardo,
I think you've basically got it, but the state is more complicated than you
think. Basically everything has a vtkSMProxy, and those proxies contain the
state of the pipeline, representation, and views. Anything that is modified
from the defaults gets saved in the state file. The
Hi,
If you set your PYTHONPATH and PATH environment variables correctly, you'll
be good. This wiki gives some pointers on how to do it:
https://www.paraview.org/Wiki/ParaView/Python_Scripting#Getting_Started
Regards,
Aron
On Sat, Nov 11, 2017 at 2:55 PM, Ke Gao wrote:
>
Yes, that Intel driver bug is known to affect ParaView:
https://gitlab.kitware.com/paraview/paraview/issues/17499
Regards,
Aron
On Tue, Dec 5, 2017 at 6:40 AM, Jonathan Borduas <
jonathan.bord...@caboma.com> wrote:
> Was the laptop running with the intel gpu ? If so, it might be related to
> an
Hi Jairaj,
This is exactly what the 'trace' and python macro functions are for. Take a
look in the Tools menu, and choose Start Trace. If you check the 'show
incremental trace' button you can see it's recording a python script as you
take actions in the GUI. When you've completed your steps, you
Hi Keith,
Yes, this is a known bug in some Intel graphics drivers, on Windows, and I
believe we've seen something similar on Linux, as well.
If your lucky enough to be running an Optimus laptop, just switching
ParaView to use the nvidia card fixes the problem.
Intel has also fixed the bug in their