| View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
| 0009674 | ParaView | Feature | public | 2009-10-07 11:50 | 2010-04-21 11:13 | ||||
| Reporter | Ken Moreland | ||||||||
| Assigned To | Utkarsh Ayachit | ||||||||
| Priority | normal | Severity | minor | Reproducibility | have not tried | ||||
| Status | closed | Resolution | fixed | ||||||
| Platform | OS | OS Version | |||||||
| Product Version | |||||||||
| Target Version | WhenPossible | Fixed in Version | 3.8 | ||||||
| Summary | 0009674: Python trace should not record default values for representation properties | ||||||||
| Description | Do 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. | ||||||||
| Tags | No tags attached. | ||||||||
| Project | |||||||||
| Topic Name | |||||||||
| Type | |||||||||
| Attached Files | |||||||||
| Relationships | |
| Relationships |
| Notes | |
|
(0020303) Utkarsh Ayachit (administrator) 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 (manager) 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 (manager) 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. |
| Notes |
| Issue History | |||
| Date Modified | Username | Field | Change |
| 2009-10-07 11:50 | Ken Moreland | New Issue | |
| 2009-10-07 11:51 | Ken Moreland | Target Version | => 3.8 |
| 2010-04-16 13:33 | Utkarsh Ayachit | Target Version | 3.8 => WhenPossible |
| 2010-04-20 17:19 | Utkarsh Ayachit | Note Added: 0020303 | |
| 2010-04-20 17:19 | Utkarsh Ayachit | Status | backlog => @80@ |
| 2010-04-20 17:19 | Utkarsh Ayachit | Fixed in Version | => 3.8 |
| 2010-04-20 17:19 | Utkarsh Ayachit | Resolution | open => fixed |
| 2010-04-20 17:19 | Utkarsh Ayachit | Assigned To | => Utkarsh Ayachit |
| 2010-04-20 17:33 | Alan Scott | Note Added: 0020310 | |
| 2010-04-20 17:33 | Alan Scott | Status | @80@ => closed |
| 2010-04-21 11:13 | Ken Moreland | Note Added: 0020332 | |
| 2011-06-16 13:10 | Zack Galbreath | Category | Feature Request => Feature |
| Issue History |
| Copyright © 2000 - 2018 MantisBT Team |