Ay, I know all that
If it would be something I’d do on shotgun I’d have to create a fields that tracks multiple custom entity’s which I’d need to set up and configure pages for.
And I’d need to save path template’s in there or keep track of the the paths in the templates.yml.
My aim is simply to keep all the configuration for this in one place and since it uses paths keys for generating client export paths I wanted to keep all related setting information in templates.yml by using keys.
And before anyone mentions “You can set settings on apps”.
That wouldnt work, basically each path key I define in the templates.yml which starts with a specific code (i.e. “ce_” for “client export”) will be read, decoded and appended to option lists.
This would create export options in a gui for client1 and client2
- client 1 has export options for only exr
- client 2 has export options for exr and mov
(Above is just an example)
Unfortunately I can’t share the code for this.
I think What I’ll do is see how badly the “extra space” fix can screw up.
The alternative now would be to read a custom text file instead of a yaml file and write my own interpreter for it, which is not a problem at all.
Just wanted to keep things in the same places