As I read the examples above, I don't think you're actually benefiting from true relative directories. If you were, there'd be no reason to specify any part of the directory structure above (outside) Project_A
Either I'm reading it wrong or your explanation is worded in a way that leads to my confusion.
When you mention Directory in each example, what does that represent? The value in the directory element of the .qtr file?
What I'm shooting for here.... given a .qtr file lives in /A/B/C/foo.qtr, that .qtr file would contain a directory element of D
Then, you'd end up with this:
/A/B/C/foo.qtr
/A/B/C/D/bar.mid
/A/B/C/D/baz.mid
Now, the C directory is the project directory meaning it could be backed up, restored onto another machine, and loading the foo.qtr file would work because it will find every artificat in the D directory.
As I read the examples above, I don't think you're actually benefiting from true relative directories. If you were, there'd be no reason to specify any part of the directory structure above (outside) Project_A
Either I'm reading it wrong or your explanation is worded in a way that leads to my confusion.
When you mention Directory in each example, what does that represent? The value in the directory element of the .qtr file?
What I'm shooting for here.... given a .qtr file lives in /A/B/C/foo.qtr, that .qtr file would contain a directory element of D
Then, you'd end up with this:
/A/B/C/foo.qtr
/A/B/C/D/bar.mid
/A/B/C/D/baz.mid
Now, the C directory is the project directory meaning it could be backed up, restored onto another machine, and loading the foo.qtr file would work because it will find every artificat in the D directory.