..\..\filename and |..\ and FileName (File Split)

Hey guys, maybe you know more… This is an example case.

In the XML of a patch, filenames to nodes, plugins, fx etc are very often saved with
-’…\folder\filename.v4p’
Filenames from pins of eg the FileTexture Node are saved as
-’…\Folder\file.jpg’
And eg the collada node saves the pin with
-’|…\folder\file.dae|’

I have a problem with that. Because if I use for example FileName(File Split) with those paths, I get for ‘…\X’ ‘C:\VVVV\vvvv_45beta29.2\folder\X’
and for ‘…\X’ ‘C:\VVVV\vvvv_45beta29.2\modules\X’

That is just very often not correct. because I dont save my stuff inside the vvvv distribution but in a parallel folder like for example C:\VVVV\vvvv_files

Can someone describe how vvvv finds the correct folder anyway?

hei tek,
can you provide a sample patch demonstrating this?

ah i just had an idea.

The …\ stands for the folder that is already clear through the first <PATCH nodename=‘C:\VVVV\folder\patch.v4p’ …> in the XML. So in this case it would mean C:\VVVV.

True?

e: no… okey wait joreg I will try to make a a example patch

the example patch works, only the special case doesnt work and I cant upload it.

My confusion about relative paths gets a a bit clearer.

…\ is relative to the path of the module that is calling it, is this correct?

And you have special cases like …\Users leads to the Users folder correctely.

But what does |…\folder\file.dae| mean? It cannot be read by a FileName node, I have to substitute the |.

e: or does … say ‘go back one folder’?

hm…it is hard to follow your musings, but one thing: the | has no meaning. just strip it. the resulting path is relative to the patchs path at runtime. note that the has no say in the resolving of that path.

yes sorry it is hard to follow. The main problem was that I was operating in the XML of a root patch with a subpatch. So the path of the subpatch was used for the relative paths. and this path was in my module folder of the vvvv distibution. After your statemant it makes sense that it didn’t work. thanks joreg!