| View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
| 0004890 | ParaView | (No Category) | public | 2007-04-16 14:33 | 2007-05-07 14:41 | ||||
| Reporter | David Karelitz | ||||||||
| Assigned To | Eric Stanton | ||||||||
| Priority | high | Severity | major | Reproducibility | unable to reproduce | ||||
| Status | closed | Resolution | unable to reproduce | ||||||
| Platform | OS | OS Version | |||||||
| Product Version | |||||||||
| Target Version | Fixed in Version | ||||||||
| Summary | 0004890: Lookmark bug with threshold filter (might be with saving state) | ||||||||
| Description | If I save a lookmark consisting of a warp(vector) followed by a threshold filter, when I apply the lookmark to a dataset, the Scalars field in the threshold filter shows the default variable instead of the scalar variable used in the lookmark. The min and max threshold values are correct | ||||||||
| Tags | No tags attached. | ||||||||
| Project | |||||||||
| Topic Name | |||||||||
| Type | |||||||||
| Attached Files | |||||||||
| Relationships | |
| Relationships |
| Notes | |
|
(0007510) Eric Stanton (reporter) 2007-04-27 16:29 |
This works for me. I applied the lookmark you describe to a reader both with the variable I'm thresholding by turned off and already turned on in the reader. It sounds like its related to the following bug that Utkarsh fixed a short time ago: Bug 0004598 - List of available variables in downstream filters does not get updated when turned on/off in reader Is the variable that you're thresholding by in the Scalars field at all? |
| Notes |
| Issue History | |||
| Date Modified | Username | Field | Change |
| 2011-06-16 13:10 | Zack Galbreath | Category | => (No Category) |
| Issue History |
| Copyright © 2000 - 2018 MantisBT Team |