[Paraview-developers] vtkSMTransferFunctionManager->GetColorTransferFunction

[Joshua Murphy]

Hi Utkarsh,

I was running into the same problem with a source I wroteŠ Basically the
source defaults to the arrays being named ³Data² regardless of what is put
in it.  Thus, even if the data is vastly different, with multiple
instances of the source, everything is getting the same color scale, even
if I assign them different within python.

So, if I read what you are saying this post, in order to separate the
individual instances of the source, it is necessary to name the arrays
differently between instantiations?  That is a world class pain. :)  I
guess I have some re-coding to do.   Glad I saw this post before I spent
all day troubleshooting!

-Josh

On 5/22/14, 7:17 AM, "Utkarsh Ayachit" <utkarsh.ayachit at kitware.com> wrote:

>Yes, that's exactly what's expected in ParaView, by design. All arrays
>with the same name get the same color transfer function. If custom
>applications want to change they, they can override (using VTK's
>factory mechanisms) the vtkSMTransferFunctionManager.
>
>Utkarsh
>
>On Thu, May 22, 2014 at 7:35 AM, Mathieu Westphal
><mathieu.westphal at gmail.com> wrote:
>> It seems to me this method associate an arrayName to a
>> ColorTransferFunction.
>>
>> It works well, but it appears that two array from completly different
>> dataset with the same name will be displayed with the exact same
>> ColorTransferFunction, including color, range and opacity.
>>
>> Is this normal ?
>>
>> Thanks
>>
>> Mathieu
>> _______________________________________________
>> Paraview-developers mailing list
>> Paraview-developers at paraview.org
>> http://public.kitware.com/mailman/listinfo/paraview-developers
>_______________________________________________
>Paraview-developers mailing list
>Paraview-developers at paraview.org
>http://public.kitware.com/mailman/listinfo/paraview-developers