state files. so to me it sounds likely
to be a different bug. if the xdmf reader makes use of the new
properties panel it may have been fixed. All of this is pure speculation
on my part. Kyle is the authority.
Burlen
On 09/13/2012 10:38 AM, Ian Curington wrote:
Hello Burlen, Kyle,
I
I would like to request Extending pqPythonManager to execute pvpython from
memory buffer rather
than exlusively from an external file (patch supplied as at
http://paraview.org/Bug/view.php?id=13456 ).
Why? Within other plugins, filters, C++ programs, can be helpful to execute
some
Hello Burlen, Kyle,
I am noticing very similar UIstate file related marked as
modified problems, and wonder if it can be related. Please see
report at: http://paraview.org/Bug/view.php?id=13317
Any suggestions?
-Ian
Wednesday, August 15, 2012, 5:20:32 PM, you wrote:
Hello Utkarsh, Mohamad,
Note we have supplied a working patch at:
http://www.paraview.org/Bug/view.php?id=13092
which includes arbitrary environment variable support in pvsm paths:
where environment can be reference using syntax of
%VAR_NAME%, ${VAR_NAME} and $VAR_NAME. In the
Title: OpenFoam reader native built-in or plugin version differences
Dear ParaView OpenFoam users:
http://openfoamwiki.net/index.php/Contrib_Parallelized_Native_OpenFOAM_Reader_for_ParaView
current SVN source is configured as a plugin, has extra buttons (Watch, Rescale),
however only mentions
Title: [ParaView] mapping PipelineSource with vtkActor names solution
Regarding resolving meaningful actor names in 3D views, I'd like to propose
adding a 1-line addition to:
ParaViewCore/ClientServerCore/vtkGeometryRepresentation.h line 185:
vtkPVLODActor* GetActor(){return Actor;}
This
Regarding resolving meaningful actor names in 3D views, I'd like to
propose
adding a 1-line addition to:
ParaViewCore/ClientServerCore/vtkGeometryRepresentation.h line 185:
vtkPVLODActor* GetActor(){return Actor;}
This will give plugin developers the minimum required handle to
make
