I’ve noticed 2 issues concerning the way ParaView works with state files (.pvsm) since upgrading from version 5.9.1 to version 5.10.1 on my Windows machine.
With version 5.9.1, I used to be able to simply double-click on a state file and the application would rerun the pipeline.
With version 5.10.1, when I double-click on a state file, ParaView seems to try to open it like it was a data file and asks me what reader to “Open Data With…” and selecting most readers simply results in an error message while some readers even cause the application to silently crash.
The steps to reproduce this error are easy: with fresh installs of both ParaView version 5.9.1 and version 5.10.1, save a state file with any one of them, then try to open it from the Windows file browser. Version 5.9 will open it successfully as a state file, but version 5.10 will prompt you to choose a reader.
Again with ParaView version 5.9.1, I used to be able to manually modify a state file to make it work with relative paths (which was necessary if I wanted to use the same state files on different computers, unless someone knows of another way to make these state files portable). Now with version 5.10.1, loading a state file containing relative paths results in an error message.
Steps to reproduce: load a data file with ParaView 5.9 or 5.10 and save a state file in the same directory as the data file. Then in a text editor (for example Notepad++), find all the lines with your data file’s location and replace the full path with a ‘.’ (for example: if your file is under “C:\Users\YOURNAME\Documents\MYDATAFILE.EXTENSION” you need to replace the full path with “.\MYDATAFILE.EXTENSION”).
Did anyone notice the same issues ? or knows of a workaround ?
Thank you in advance !