It would be useful for user who open paraview from *.pvsm to do batch process.
ParaView 5.6.0
I’m not sure what is the usecase here. Could you give more precision ?
user open paraview from *.pvsm (delat_v_e4_1p.pvsm)
So you want to be able to show the name of the .pvsm file used in the File->LoadState in all the views loaded by the state ?
I’m not sure we want that.
Do I make myself more clear?
In my case, *.pvsm contains the same *.foam
Yes, very clear. But the .pvsm file is not related to the OpenFOAMReader. It would not make sense to display it.
The pipeline of a loaded state if the same as if it was created manually, we can’t discriminate between one and the other.
It would not make sense to display it.
it → *.pvsm?
yes
ParaView knows how to open a file with *.foam extension.
ParaView knows how to do with it.
ParaView knows how to open a file with *.pvsm extension.
ParaView can open with it with many filters.
So, I think ParaView stores some info about input argument.
ps.
@mwestphal
I would like to investigate the source code.
Could you give me some reference to it?
I would like to contribute my effort.
So, the conclusion, is:
It is not possible, now, to show /PATH/TO/*.pvsm as the function:
Display File Path does?
ParaView can different open a file with *.foam extension.
Yes ?
ParaView knows how to do with it.
Yes.
ParaView know how to open a file with *.pvsm extension.
Yes and no. A .pvsm file is a state file that describe a full pipeline. It is not open by a reader but by the state loader. As you can see, File → Open and File → LoadState is not the same thing.
ParaView can open it with many filters.
No. A .pvsm is opened by the state loaded.
it is not possible, now, to show /PATH/TO/*.pvsm as the function:
If you refer to the OpenFOAM property. It is not possible and never will be.
Could you give me some reference to it?
https://kitware.github.io/paraview-docs/latest/cxx/classvtkSMStateLoader.html
1 Like