[Paraview] pathnames in .pvsm files
berk.geveci at kitware.com
Fri Oct 26 18:49:47 EDT 2007
I'd say go ahead and submit a feature request. This (paths relative to
pvsm) is a very useful feature we should implement.
On 10/25/07, Andrew Maclean <andrew.amaclean at gmail.com> wrote:
> This is an issue relating to cross-platform usage of the ParaView .pvsm
> The problem I have is that when I create a .pvsm file under Windows and then
> move the file and associated datafiles to Linux, the absolute pathnames to
> the data files won't work (obviously). I now hand edit the file and convert
> the pathnames to relative pathnames which seems to work Ok.
> How difficult would it be to use relative paths (relative to the .pvsm file)
> and add the path to the .pvsm file when locating the datafiles.
> E.g If I created the .pvsm file in Windows my datafile may be called:
> "C:\Documents and Settings\amaclean\My
> However if I am in Linux the datafile will end up in some directory such as:
> So would it be possible to store these paths as relative to where the .pvsm
> file is stored? E.g ./bench.vtp and then let ParaView add the pathname of
> the .pvs, file to these names?
> Are there any problems/issues that the developers can see?
> I am happy to add it as a feature request if people think it is worthwhile
> (I do as we have people working on different platforms in the field without
> a central file server).
> Andrew J. P. Maclean
> Centre for Autonomous Systems
> The Rose Street Building J04
> The University of Sydney 2006 NSW
> Ph: +61 2 9351 3283
> Fax: +61 2 9351 7474
> URL: http://www.acfr.usyd.edu.au/
> ParaView mailing list
> ParaView at paraview.org
More information about the ParaView