Dear Jeff,
I cannot really help you with your questions since i am not familiar
with the Paraview source. However, your email sounds as if you are
planning to - after understanding how stereo rendering is implemented in
Paraview - include some improvements there. If you do so, i would like
to
I am looking at some of the stereo rendering currently in ParaView
(initially just by invoking the --stereo option at the command line).
I have quite a bit of experience with stereo rendering both as a user
and as a developer, and I can immediately see some problems with the
stereo rendering I
Hi
I am new to ParaView. I want to visualize scalar data but I do not have
values of the scalar function at all the nodes. Can ParaView interpolate the
values at these nodes as well?
Any help would be greatly appreciated. Thank you.
___
Powered by www.k
Thanks for reporting this Lawrence. I'll take a look and get back to you soon.
Utkarsh
On Thu, Aug 4, 2011 at 12:12 PM, Lawrence Angrave wrote:
> Hi,
> We've found that a very simple 10x10x10 volumetric dataset causes paraview
> stable (3.10.1) to crash when the representation is changed to Vol
Hi,
We've found that a very simple 10x10x10 volumetric dataset causes
paraview stable (3.10.1) to crash when the representation is changed to
Volume.
We've reproduced this on Windows and Mac builds.
The crash is is in vtkVolumeRayCastSpaceLeapingImageFilterMinMaxExecute
tmpPtrI = tmpPtrJ
Nope, this is not possible through plugins yet. You can add a
brand-new dock widget through plugins but not add a new tab to the
Object Inspector widget.
Utkarsh
On Thu, Aug 4, 2011 at 11:56 AM, Brian C. Panneton (CONTR)
wrote:
> I was wondering if there was an example of how to add a new tab to
I was wondering if there was an example of how to add a new tab to the
Object Inspector for a plugin. I remember being told that it is
possible, but I can't seem to find any examples.
Thanks,
Brian Panneton
___
Powered by www.kitware.com
Visit other
I think I have solved the issue I was having just now. I could not pursue it
for a while because of other job priorities and we were at the time still
having a functioning system with ParaView v3.8.1. This is the reason of the
late reply.
I have managed to have a working solution for the follow