View Issue Details [ Jump to Notes ] [ Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0014830ParaView(No Category)public2014-06-27 21:472014-08-29 10:59
ReporterAlan Scott 
Assigned ToCory Quammen 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Versiongit-master 
Target Version4.2Fixed in Version4.2 
Summary0014830: Color editor, Mapping data, sometimes goes insane
DescriptionThe color editor, mapping data section sometimes goes insane. Here is a reliable way to replicate:

* Linux, master, local server.
* Open disk_out_ref.exo. All vars on. Apply.
* Slice. Apply.
* Turn off "Show plane".
* +X. Reset.
* Color by GaMe3.
* Open the color editor.
<<Bug>> - notice that the upper triangular graphic's colors are crazy. They are red on the right, grading left to white (where they should have white in the middle, grading left to blue).

TagsNo tags attached.
ProjectSandia
Topic Name14830_initial_opacity_function_display
Typeincorrect functionality
Attached Files

 Relationships

  Notes
(0032968)
Cory Quammen (developer)
2014-07-04 09:49

 I can confirm this bug, even when simply loading the disk_out_ref.ex2 dataset and coloring the surface by GaMe3 (or any other array). Resetting to the data range to the full range doesn't fix it - it actually makes the display worse. Resetting to a custom range does fix it, seemingly for the rest of the session with that array.
(0032969)
Cory Quammen (developer)
2014-07-05 15:25

 commit 644f7df84bcdc98465601439bc09bfe811759a13
Author: Cory Quammen <cory.quammen@kitware.com>
Date: Fri Jul 4 22:06:21 2014 -0400

    BUG 14830: Fixed initial display of opacity function editor
    
    The initial range of the scalar opacity function was not set
    correctly. Added a property "ScalarRangeInitialized" to the
    PiecewiseFunction proxy that indicates whether the scalar opacity
    function was initialized. This is the same property added to the
    PVLookupTable proxy that makes the color lookup table initial display
    work correctly. Its absence from the PiecewiseFunction proxy was
    causing this bug.
    
    Change-Id: I72096e947c871bee6a8438abdf207639202fffae
(0033011)
Utkarsh Ayachit (administrator)
2014-07-11 09:54

 SUMMARY
---------------------------------------------
Topics merged into master:
        0014846-update-benchmarks
        13575_site_settings_search_paths
        14830_initial_opacity_function_display
        api_cleanup
        avi-compression
        dashboard-warnings
        tree_widget_height
        volume-rendering-catalyst
(VTK) vtkweb-arg-for-custom-ws-endpoint
(0033098)
Alan Scott (manager)
2014-07-25 21:03

 Tested master, Linux, local server.

 Issue History
Date Modified Username Field Change
2014-06-27 21:47 Alan Scott New Issue
2014-06-28 08:18 Utkarsh Ayachit Target Version => 4.2
2014-07-04 09:49 Cory Quammen Note Added: 0032968
2014-07-04 09:49 Cory Quammen Assigned To => Cory Quammen
2014-07-04 09:49 Cory Quammen Status backlog => active development
2014-07-05 15:25 Cory Quammen Topic Name => 14830_initial_opacity_function_display
2014-07-05 15:25 Cory Quammen Note Added: 0032969
2014-07-05 15:25 Cory Quammen Status active development => gatekeeper review
2014-07-05 15:25 Cory Quammen Fixed in Version => git-next
2014-07-05 15:25 Cory Quammen Resolution open => fixed
2014-07-11 09:54 Utkarsh Ayachit Fixed in Version git-next => git-master
2014-07-11 09:54 Utkarsh Ayachit Status gatekeeper review => backlog
2014-07-11 09:54 Utkarsh Ayachit Note Added: 0033011
2014-07-16 16:47 Utkarsh Ayachit Status backlog => gatekeeper review
2014-07-16 16:47 Utkarsh Ayachit Status gatekeeper review => customer review
2014-07-25 21:03 Alan Scott Note Added: 0033098
2014-07-25 21:03 Alan Scott Status customer review => closed
2014-08-29 10:59 Utkarsh Ayachit Fixed in Version git-master => 4.2

Copyright © 2000 - 2018 MantisBT Team