Ah interesting. I wasn't aware of that change. Thanks.
Utkarsh
On Mon, May 23, 2011 at 1:26 PM, Nenad Vujicic wrote:
> Dear Utkarsh,
>
> Yes, it works perfectly with ParaView v3.8.* release sources. The
> reason is in vtkScalarsToColorsPainter class which produces 256x1
> texture in ParaView v3.
Dear Utkarsh,
Yes, it works perfectly with ParaView v3.8.* release sources. The
reason is in vtkScalarsToColorsPainter class which produces 256x1
texture in ParaView v3.8.*, while in ParaView 3.10.* (and current SVN
sources) it produces 256x2 texture. In v3.10.* case, in first row
(bottom-up) are
Interesting, I wonder how that could have worked with older version of
ParaView then. Did that piece of code change recently?
Utkarsh
On Sun, May 22, 2011 at 2:43 PM, Nenad Vujicic wrote:
> Hello everyone,
>
> Just to announce - the problem is solved! It seems the problem was in
> plugin's sourc
Hello everyone,
Just to announce - the problem is solved! It seems the problem was in
plugin's sources when setting texture coordinates data. So, if in
vtkMyExporter.cpp I remove
tex_coord_data->SetNumberOfComponents(1);
or set number of components to 2, correct texture will be generated!
Thank
Hello everyone,
Does anyone have idea where could be the problem in uploaded sources?
Thanks,
Nenad.
On Tue, May 10, 2011 at 12:13 PM, Nenad Vujicic wrote:
> Dear Utkarsh,
>
> Thank You very much, but unfortunately, adding manually copying of
> parameters didn't solve all problems. I updated te
Dear Utkarsh,
Thank You very much, but unfortunately, adding manually copying of
parameters didn't solve all problems. I updated test plug-in with
manually copying, converting scalars to texture, applying texture to
actor and showing resulting actor in vtkRenderWindow. You can find
updated sources
The problem is pretty straight forward. Looks like
vtkMapper::ShallowCopy(..) does not copy the state of
InterpolateScalarsBeforeMapping. I will commit a fix for that for next
release. Until then, you'll have to manually copy ivars that you care
about.
Utkarsh
On Sun, May 8, 2011 at 10:25 AM, Nen
Dear Utkarsh,
I uploaded test plugin that shows my problem at
http://alas.matf.bg.ac.rs/~mr00053/projects/PVTest.zip.
After I build and load the plugin from Qt client, I load
disk_out_ref.ex2, select "H2" for mapping scalars, check Interpolate
Scalars on Display tab in Object inspector and go on
Nenad,
There;s nothing much different about the vtkCompositePolyDataMapper or
vtkPolyDataMapper as far as the state of the
InterpolateScalarsBeforeMapping flag goes. I cannot see how that
variable can return false if it is indeed set to true as you are
saying. Can you share the plugin?
Utkarsh
O
Hello everyone,
Perhaps I was a bit unclear in my previous messages. Here are more
details about the problem and test case.
I use ParaView v3.10.1 release sources, Visual Studio 2008 SP1, Python
2.7, OpenMPI 1.4.3 on Vista SP2. I compiled sources with standard
options (just turned on BUILD_SHARED
Dear Utkarsh,
Thank You very much on Your answer.
Yes, my plug-in is exporter, which means I define it in class derived
from vtkExporter. It extracts all possible scene information from
vtkExporter::RenderWindow object (in both Qt-client and python-client
modes) and writes these data to very spec
Nenad,
I am not sure I understand where this code is being put. You say it's
an exporter? Meaning it exports to something like a vrml/x3d file? But
that doesn't seem right since you say you are using the
PolyDataMapper.
What is this plugin trying to achieve?
Utkarsh
On Wed, May 4, 2011 at 8:31
Hello everyone,
I'm having some problems with porting my ParaView exporter plug-in to
v3.10, because ParaView started using vtkCompositeDataSet internally
instead of keeping components merged. The problem is in performing
transformation of scalars to texture using vtkScalarsToColorsPainter
class.
13 matches
Mail list logo
