Hi!
I'd like to know if it is possible to set properties to some value
without letting the user change that. This would be nice, since e.g. the
vtkImageGaussianSmooth requires a call SetDimensionality to setup
whether to use a 1D, 2D or 3D Gaussian Smooth. Depending on that the
user has to
I think you could set the show hint in the server manager XML. for eg
SourceProxy ...
...
IntVectorProperty
name=Dimensionailty
command=SetDimensionality
number_of_elements=1
default_values=2
/IntVectorProperty
...
Hints
Property name=Dimensionality show=0/
/Hints
/SourceProxy
Thanks, Dave. I really appreciate all of the work on the install and packaging
stuff, and how quickly you've been making the changes we need.
Talk to you later,
-Eric
On Mar 16, 2010, at 11:30 AM, Dave Partyka wrote:
Hi Eric, try now. I have moved that file into ParaView\CMake (as it is only
On Wed, 2010-03-17 at 09:01 -0400, Eric E. Monson wrote:
Thanks, Dave. I really appreciate all of the work on the install and
packaging stuff, and how quickly you've been making the changes we
need.
Agreed - it's nice to see that we are now able to build a paraview that
can relocated and still
Posting back to the mailing list to see if anyone else has any idea
what's going on.
On Tue, Mar 16, 2010 at 12:08 PM, SCHROEDER, Martin
martin.schroe...@mtu.de wrote:
Hm, i don't think it's broken, because wit works under some circumstances (on
one only host, on multiple hots with pvserver
On 17. Mar, 2010, at 15:19 , paraview-requ...@paraview.org wrote:
You will probably have to use ParaView from CVS Head in order to fix
the Carbon/Cocoa thing. There is a quick patch you can do to a stock
ParaView 3.6.2 to fix the problem if you want.
Hey again,
At least as things naturally happen on my Ubuntu machine, there is definitely
something wrong with the test for whether FFMPEG has old headers (setting
VTK_FFMPEG_HAS_OLD_HEADER):
Building the old ffmpeg downloaded from the VTK site, according to Dave
DeMarle's README instructions,
Dear paraview list:
I am new to using paraview, and I would appreciate your help with the
following question. In our group, we have some old state files (*.pvs
extension) that were created with paraview version 2.6 (according to
the header of the file). I cannot load these .pvs state files
Amy,
ParaView has under went fundamental changes since 2.6 and hence we do
not support importing 2.6 or earlier state files since 3.0.
Utkarsh
On Wed, Mar 17, 2010 at 3:41 PM, Amy Bengtson am...@umich.edu wrote:
Dear paraview list:
I am new to using paraview, and I would appreciate your
Paraview appears to have a limited ability certain plot3D files that
were likely generated from C/C++ code, but is unable to read plot3D
files generated from Fortran code. When I open a Fortran generated
plot3D file I select plot3D as the file type and then select the
following three
Yes, I have also generated an ASCII plot3D file, which I can get
paraview to read. However, paraview does not correctly interpret the
grid file. The geometry I create with my simple Fortran code is a
cube. Paraview successfully reads both the ASCII grid and data files,
but when I view
11 matches
Mail list logo