Loading identical .py state and .pvsm states give inconsistent results
I’m having a ParaView state saved as .pvsm gives correct position of colorbars and other elements. However, when the same state is stored and loaded as a .py script the colorbars get misplaced. What is the issue? (version: ParaView 5.10.1) I’m putting in the relevant images.
Loading .pvsm state:
Misplaced colorbars on loading .py state produced at the same time in the GUI:
The placement of the colorbars become consistent when the .py script is loaded and generated in ParaView 5.11.0 version compared to the inconsistencies in 5.10.1 version. However, the font sizes are still in-consistent and don’t give identical results. The same happens if I change the orientation axes position (not shown in these images), the python saved state keeps the orientation axes at the default lower left position but the .pvsm file works correctly and puts the orientation axes at the changed location. As a result of the font size inconsistency, parts of the text get cut off at the edges. Also, most likely because of this, same issues happen for Catalyst python states as well. Can someone more experienced in the community help me fix this issue?
Here is the screenshot of what happens on loading the .py state script in ParaView 5.11.0: