| View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
| 0008278 | ParaView | (No Category) | public | 2008-12-10 20:42 | 2009-05-13 13:46 | ||||
| Reporter | Alan Scott | ||||||||
| Assigned To | Utkarsh Ayachit | ||||||||
| Priority | normal | Severity | feature | Reproducibility | always | ||||
| Status | closed | Resolution | fixed | ||||||
| Platform | OS | OS Version | |||||||
| Product Version | |||||||||
| Target Version | 3.6 | Fixed in Version | |||||||
| Summary | 0008278: Color legend should be on or off - and track the color by variable. | ||||||||
| Description | Feature request from a user (and a good idea). When using the color legend, this color legend should remain either on or off, no matter what variable you choose. It should also follow the variable. Example: Open disk_out_ref.exo. All variables on. Apply. Color by Temp. Toggle Color Legend Visibility. Color by Pres. << Color legend should stay up, and it should change to Pres.>> Note - are there cases we would not want this behavior - for instance if we are also displaying stuff from a previous filter using a different variable? | ||||||||
| Tags | No tags attached. | ||||||||
| Project | |||||||||
| Topic Name | |||||||||
| Type | |||||||||
| Attached Files | |||||||||
| Relationships | ||||||
|
||||||
| Relationships |
| Notes | |
|
(0015525) Utkarsh Ayachit (administrator) 2009-03-03 17:21 |
Consider this case: disk_out_ref (wireframe) --> Slice (surface) Both are visible and being colored with "Temp". The scalar bar is also visible. Now if the user changes disk_out_ref to color by "Pres", we have two options: * show "Pres" scalar bar and hide "Temp" scalar bar (even though Slice is using it) * show "Pres" scalar bar and leave "Temp" scalar bar visible as well Which is a more acceptable solution? |
|
(0015527) Alan Scott (manager) 2009-03-03 22:15 |
OK, thinking out loud - Taking the example above. disk_out_ref (wireframe). It is colored by something (Temp). If it has a scalar bar visible, it will track whatever disk_out_ref is being colored by. slice (surface). It is colored by something. If it has a scalar bar visible, it will track whatever slice is being colored by. There may be two scalar bars up, at the users request. They may be tracking the same thing. Now, if user changes disk_out_ref to color by Pres, the disk_out_ref scalar bar is Pres, the slice scalar bar tracks Temp. I know that this idea may not be easy ... :-/ Thoughts? |
|
(0015539) Utkarsh Ayachit (administrator) 2009-03-04 14:00 |
If color by array is changed and the scalar bar of the previous array is shown, then the scalar bar for the new array will be shown as well. /cvsroot/ParaView3/ParaView3/Qt/Components/pqColorScaleEditor.cxx,v <-- Qt/Components/pqColorScaleEditor.cxx new revision: 1.52; previous revision: 1.51 /cvsroot/ParaView3/ParaView3/Qt/Components/pqPQLookupTableManager.cxx,v <-- Qt/Components/pqPQLookupTableManager.cxx new revision: 1.16; previous revision: 1.15 /cvsroot/ParaView3/ParaView3/Qt/Components/pqPQLookupTableManager.h,v <-- Qt/Components/pqPQLookupTableManager.h new revision: 1.7; previous revision: 1.6 /cvsroot/ParaView3/ParaView3/Qt/Core/pqLookupTableManager.cxx,v <-- Qt/Core/pqLookupTableManager.cxx new revision: 1.4; previous revision: 1.3 /cvsroot/ParaView3/ParaView3/Qt/Core/pqLookupTableManager.h,v <-- Qt/Core/pqLookupTableManager.h new revision: 1.7; previous revision: 1.6 /cvsroot/ParaView3/ParaView3/Qt/Core/pqPipelineRepresentation.cxx,v <-- Qt/Core/pqPipelineRepresentation.cxx new revision: 1.39; previous revision: 1.38 /cvsroot/ParaView3/ParaView3/Qt/Core/pqScalarBarRepresentation.cxx,v <-- Qt/Core/pqScalarBarRepresentation.cxx new revision: 1.10; previous revision: 1.9 /cvsroot/ParaView3/ParaView3/Qt/Core/pqScalarBarRepresentation.h,v <-- Qt/Core/pqScalarBarRepresentation.h new revision: 1.8; previous revision: 1.7 /cvsroot/ParaView3/ParaView3/Qt/Core/pqScalarBarVisibilityAdaptor.cxx,v <-- Qt/Core/pqScalarBarVisibilityAdaptor.cxx new revision: 1.10; previous revision: 1.9 |
|
(0015584) Alan Scott (manager) 2009-03-05 16:12 |
Wow, this is nice. Tested client/ remote server |
| Notes |
| Issue History | |||
| Date Modified | Username | Field | Change |
| 2008-12-10 20:42 | Alan Scott | New Issue | |
| 2009-02-17 15:34 | Utkarsh Ayachit | Status | backlog => tabled |
| 2009-02-17 15:34 | Utkarsh Ayachit | Assigned To | => Utkarsh Ayachit |
| 2009-02-18 08:46 | Utkarsh Ayachit | Relationship added | related to 0007563 |
| 2009-03-03 17:21 | Utkarsh Ayachit | Note Added: 0015525 | |
| 2009-03-03 17:21 | Utkarsh Ayachit | Status | tabled => @20@ |
| 2009-03-03 22:15 | Alan Scott | Note Added: 0015527 | |
| 2009-03-04 14:00 | Utkarsh Ayachit | Note Added: 0015539 | |
| 2009-03-04 14:00 | Utkarsh Ayachit | Status | @20@ => @80@ |
| 2009-03-04 14:00 | Utkarsh Ayachit | Resolution | open => fixed |
| 2009-03-04 14:04 | Utkarsh Ayachit | Relationship replaced | has duplicate 0007563 |
| 2009-03-05 16:12 | Alan Scott | Note Added: 0015584 | |
| 2009-03-05 16:12 | Alan Scott | Status | @80@ => closed |
| 2009-05-13 13:46 | Utkarsh Ayachit | Target Version | => 3.6 |
| 2011-06-16 13:10 | Zack Galbreath | Category | => (No Category) |
| Issue History |
| Copyright © 2000 - 2018 MantisBT Team |