MantisBT - ParaView
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0009674ParaViewFeaturepublic2009-10-07 11:502010-04-21 11:13
ReporterKen Moreland 
Assigned ToUtkarsh Ayachit 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version 
Target VersionWhenPossibleFixed in Version3.8 
Project
Topic Name
Type
Summary0009674: Python trace should not record default values for representation properties
DescriptionDo the following.

1. Turn on Python trace.
2. Create a Sphere source. Apply.
3. Turn off Python trace.
4. Show the trace.

The trace should be a really simple script. It should call Sphere() to create the sphere, Show() the sphere, perhaps change the render view camera position, and call Render(). What is also added to the script are a bunch of parameters to the representation that are really default values for the current settings. For example, things like EdgeColor and SelectionPointLabelJustification are set. I am now also noticing properties like RadiusTableValues being set to a long list. These are probably due to me having the point sprite plugin loaded.

The Python trace really needs to identify that these values were set off of defaults (even if they do not match the initial "default" values defined in the SM XML). This can be tricky as the "default" values might actually come from ParaView settings.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2009-10-07 11:50Ken MorelandNew Issue
2009-10-07 11:51Ken MorelandTarget Version => 3.8
2010-04-16 13:33Utkarsh AyachitTarget Version3.8 => WhenPossible
2010-04-20 17:19Utkarsh AyachitNote Added: 0020303
2010-04-20 17:19Utkarsh AyachitStatusbacklog => @80@
2010-04-20 17:19Utkarsh AyachitFixed in Version => 3.8
2010-04-20 17:19Utkarsh AyachitResolutionopen => fixed
2010-04-20 17:19Utkarsh AyachitAssigned To => Utkarsh Ayachit
2010-04-20 17:33Alan ScottNote Added: 0020310
2010-04-20 17:33Alan ScottStatus@80@ => closed
2010-04-21 11:13Ken MorelandNote Added: 0020332
2011-06-16 13:10Zack GalbreathCategoryFeature Request => Feature

Notes
(0020303)
Utkarsh Ayachit   
2010-04-20 17:19   
A while ago we added support for overriding default values for exposed properties. That gets rid of whole lot of property changes after Show() when tracing.
(0020310)
Alan Scott   
2010-04-20 17:33   
The trace code has been greatly improved. Please write a new bug with specific suggestions if this is still considered an issue.

Tested trunk, Windows, local server.
(0020332)
Ken Moreland   
2010-04-21 11:13   
It's much better, so I think it's OK to close for now. This might come back and need to be opened again. For example, if you have the point sprite plugin installed, you get a whole bunch of pointless entries in the representation again (because it adds a new representation type). The point is that as new features pop up (especially rendering features), the python scripts might become polluted enough to justify revisiting this issue.