ParaView seems to append all custom filters to any statefile that is saved (even custom filters that are not used), and further stores any custom filter, that is read from a statefile, in the local config.
This way, custom filters spread like viruses. We noticed this, when a member of our lab created a custom filter using an external plugin, that is no longer available. Anyone, who loaded one of his statefiles, was greeted with an error message, and all future saved statefiles had the same effect on any unsuspecting user’s ParaView.
To reproduce:
- Load the example statefile example.pvsm (1.9 KB)
- (optional) restart ParaView -> error message is printed
- Save a new statefile
- Delete your ParaView config (or pass the statefile to someone else) and load the new statefile -> error message is printed
- goto 3
Of course, this can be easily fixed by deleted the corresponding custom filter via Tools->Manage Custom Filters, but since most of us never used this feature, it took us a while to figure that out.