Utkarsh,
No problem.
Cory
On Mon, Jun 3, 2013 at 5:02 PM, Utkarsh Ayachit
wrote:
> For better, or for worse, that's an assumption we made in ParaView
> from the get go and hence it's not possible to support unnamed arrays
> without extensive re-factoring.
>
> Utkarsh
>
> On Mon, Jun 3, 2013 at
For better, or for worse, that's an assumption we made in ParaView
from the get go and hence it's not possible to support unnamed arrays
without extensive re-factoring.
Utkarsh
On Mon, Jun 3, 2013 at 3:14 PM, Cory Quammen wrote:
> Ah, never mind. I forgot to set a name for the array.
>
> If I ad
Ah, never mind. I forgot to set a name for the array.
If I add
bestDimensionsArray->SetName( ... );
the field data array shows up as expected.
It seems like you should still be able to see the array values if the
array doesn't have a name, though.
Cory
On Mon, Jun 3, 2013 at 3:05 PM, Cory Qu
Hi all,
I have a custom VTK filter that I am using to create a ParaView
filter. I'd like to store some information about the output from the
filter in the output's field data. My filter sets the field data for
this output as follows:
vtkPolyData *output1 = vtkPolyData::SafeDownCast(
outputV
