|
Hmmm, definitely a better suggestion. Not a fan of the load/save buttons idea but supoorting templates in those metadata fields I like. One alternative is to just make an assumption that if the user puts a template into a metadata field (starting with a {) then that becomes data that can be saved with the other cover configuration. They don’t “have” to save it (will just get nagged about unsaved changes like with other config changes) but they could.
|