Has anyone here used the `@NamdConfig` with SS2.1 ...
# sdf
k
Has anyone here used the
@NamdConfig
with SS2.1 and a bundle? Struggling to work out the documentation on bundle virtual paths. Or is it best to just stick with relative paths in the define statement?
n
I have found out that relative paths work the best.
after so much struggle to make amd config work.
k
would just be nice not to have to go to each file to update the path if the file changes location
s
the big limitation I found is @Namdconfig only applies to top level scripts
I couldn't get it to work for libraries, which renders it fairly useless
k
yeah i think that is going to be an issue with multiple libraries with libraries within libraries being specified.
s
so I root all SS2 scripts in a top level folder (named SS2) and use relative paths from there.
k
Unfortunately this is a huge bundle and that is not possible.
s
it's always possible to have a single root
otherwise your harddrive wouldn't work 🙂
anyway, sorry that AmdConfig isn't as awesome as it could be.
k
true so yeah we do have a top level folder but it's the json config file when used in libraries which ref libraries. mulitple folder upon folder with relative paths everywhere. going to be put on the back burner for now anyway
Would have made life so much simpler.