ParaView Plugin
Jump to navigation
Jump to search
Installation
- ParaView patch
- BULID_SHARED_LIBS on
- ParaView plugin
- VisTrails plugin version
- plugin paths
Usage
- Data and state files are absolute - they must exist in the same location to replay any VisTrail operations
How it works
- Types of operations:
- Generic changes that get put on the undo stack.
- State file load.
- Must be replayed from version 0 since these cannot be undone.
- Anything else that doesn't get put on the undo stack will not be captured and therefore not replay correctly!
- ParaView / VisTrails message loops.
Known issues
- Has only been tested with local ParaView server configuration.
- Has only been tested on Windows.
- Loading ParaView with VisTrails already running.
- VisTrails captures some initialization of ParaView.
- Haven't seen this happen when the ParaView plugin spawns the VisTrails process itself.