[Paraview] PV 3.81 color legend multiple views

[Moreland, Kenneth]

That behavior is not incorrect.  ParaView is supposed to synchronize the color map of all fields with the same name regardless of which pipeline object the data comes from or what view they are in.  This is an important feature that prevents confusion when interpreting field values and also avoids the headache of having to change the colors of the same field over and over again.

If the development version allows you to declare different color maps for the same variable, then that is a bug and should be fixed before the 3.10 release.  However, I tried both 3.8.1 and the development build from last night and it appears that the color map is synchronizing just fine (although you usually have to force a render in other views to update to changes in the color map).

-Ken


On 11/30/10 8:45 AM, "Andy Bauer" <andy.bauer at kitware.com> wrote:

Hi Stephen,

I get the same incorrect/linked behavior for 3.8.1.  I tried it out and this has been fixed in the development version.  The 3.10 release candidate should be ready in a week or two and this fix ought to be in that.

Andy

On Tue, Nov 30, 2010 at 4:17 AM, Stephen Wornom <stephen.wornom at inria.fr> wrote:
I have two paraview file (PV1 and PV2). I split the screen and open PV1 in the left screen and PV2 in the right screen. I make pressure surfaces. The two view are different and correct.
The problem: When I activate the color legends for PV1 and PV2, the scale is the same for both views even though the views are not linked. What I expected was two different legends corresponding to PV1 and PV2.

What am I doing incorrectly?
Thanks,
Stephen


   ****      Kenneth Moreland
    ***      Sandia National Laboratories
***********
*** *** ***  email: kmorel at sandia.gov
**  ***  **  phone: (505) 844-8919
    ***      web:   http://www.cs.unm.edu/~kmorel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.paraview.org/pipermail/paraview/attachments/20101130/5eb03304/attachment.htm>