'Re: [Paraview] PV 3.81 color legend multiple views'

[prev in list] [next in list] [prev in thread] [next in thread] 

List: paraview
Subject: Re: [Paraview] PV 3.81 color legend multiple views
From: Andy Bauer <andy.bauer () kitware ! com>
Date: 2010-11-30 16:21:31
Message-ID: AANLkTikXSFLUf1Hd+R2r9gYmx6cb1=uq21bYF3_eZXUu () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]

Hi Ken,

If that is the desired behavior then there is a bug.  You can see from the
attached image that I'm getting that behavior.  This happens when I rescale
the data range in one window.  When I change the active view though it
updates properly so that the legends are again in sync.  This out-of-sync
behavior doesn't happen in 3.8.1 but does happen in my development version.

Stephen, I didn't notice before that it synced when the view was changed so
my information was incorrect.  To get around this behavior though you can
use the calculator filter to create a second copy of the array with a
different name and then create unsynced legends.

I'll file a bug report.

Andy

On Tue, Nov 30, 2010 at 11:03 AM, Moreland, Kenneth <kmorel@sandia.gov>wrote:

>  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@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@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@sandia.gov
> **  ***  **  phone: (505) 844-8919
>     ***      web:   http://www.cs.unm.edu/~kmorel<http://www.cs.unm.edu/%7Ekmorel>
>
>

[Attachment #5 (text/html)]

Hi Ken, If that is the desired behavior then there is a bug. You can see from \
the attached image that I&#39;m getting that behavior. This happens when I rescale \
the data range in one window. When I change the active view though it updates \
properly so that the legends are again in sync. This out-of-sync behavior \
doesn&#39;t happen in 3.8.1 but does happen in my development version. \
 Stephen, I didn&#39;t notice before that it synced when the view was changed so \
my information was incorrect. To get around this behavior though you can use the \
calculator filter to create a second copy of the array with a different name and then \
create unsynced legends. I&#39;ll file a bug report. Andy <div \
class="gmail_quote">On Tue, Nov 30, 2010 at 11:03 AM, Moreland, Kenneth &lt;<a href="mailto:kmorel@sandia.gov">kmorel@sandia.gov</a>&gt; \
wrote: <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; \
border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">

<div>
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).

<br>
-Ken<br>
<br>
<br>
On 11/30/10 8:45 AM, &quot;Andy Bauer&quot; &lt;<a \
href="http://andy.bauer@kitware.com" target="_blank">andy.bauer@kitware.com</a>&gt; \
wrote:<br> <br>
</span></font><blockquote><font face="Calibri, Verdana, Helvetica, Arial"><span \
style="font-size: 11pt;">Hi Stephen,<br> <br>
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.<br> <br>
Andy<br>
<br>
On Tue, Nov 30, 2010 at 4:17 AM, Stephen Wornom &lt;<a \
href="http://stephen.wornom@inria.fr" target="_blank">stephen.wornom@inria.fr</a>&gt; \
wrote:<br> </span></font><blockquote><font face="Calibri, Verdana, Helvetica, \
Arial"><span style="font-size: 11pt;">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.<br>

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.<br> <br>
What am I doing incorrectly?<br>
Thanks,<br>
Stephen<br>
</span></font></blockquote></blockquote><font face="Calibri, Verdana, Helvetica, \
Arial"><span style="font-size: 11pt;"><br> </span></font><font size="2"><font \
                face="Consolas, Courier New, Courier"><span style="font-size: \
                10pt;"><br>
   ****      Kenneth Moreland<br>
    ***      Sandia National Laboratories<br>
***********  <br>
*** *** ***  email: <a href="http://kmorel@sandia.gov" \
                target="_blank">kmorel@sandia.gov</a><br>
**  ***  **  phone: (505) 844-8919<br>
    ***      web:   <a href="http://www.cs.unm.edu/%7Ekmorel" \
target="_blank">http://www.cs.unm.edu/~kmorel</a><br> </span></font></font><font \
face="Calibri, Verdana, Helvetica, Arial"><span style="font-size: 11pt;"><br> \
</span></font> </div>

</blockquote></div><br>

--002215974b02e2b18d04964794d6--

["legends.png" (image/png)]

_______________________________________________
Powered by www.kitware.com

Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView

Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview

[prev in list] [next in list] [prev in thread] [next in thread] 