Hi, I’m trying to get the path where my patch is located but I can’t find how…
If you use a path IOBox and leave it blank, it will be the path of the VL document or the exported exe. If you enter something into it, it will be relative to the VL document or exe.
for example /images/img.png
will load an image in a folder next to the VL document. The IO will however display the full path but will save it as a relative path.
https://thegraybook.vvvv.org/reference/language/ioboxes.html#paths
Hi @tonfilm , I’m facing an issue similar to this: I’m getting String instead of Path from a node (XPathGetValue). So even if I pass this string to a Path IOBox via ToPath node, it won’t consider it as a relative path to the VL document.
Is there an alternate way to get the path of the current VL document?
Try the ApplicationPath node @ajitid
I made a node like this a while ago.
I’m still unsure, due to the slightly weird UI/UX, whether relative paths work in input fields or not.
If anyone can shed some light on this, especially within exported applications, please clarify how best to do this. I’m using this node for now because it guarantees functionality and has a number of additional features.
AssetPath.vl (28.0 KB)
The explanation is there somehow, but it doesn’t seem to clarify the situation. Why is that? Is it convenient? How do you see which path is actually written? It feels very uncomfortable this way, I have a “memory” that this thing has let me down more than once.
I tried it, and it actually kind of works, but to put it mildly, it feels unreliable and slightly unfinished. Is it definitely guaranteed to work? Is it possible to somehow mark this field so that the path in it is relative? I’d say even more, when I patch, I’d like to see the relative path more than the absolute path. You can also see with your own eyes the bug with typing “.\” - if you start typing again, you get just “\”.
I think this field could benefit from a tooltip when hovering.