On 18 October 2015 at 19:50, Dirk Hohndel <[email protected]> wrote: > > So we are back to "the shipped templates stay immutable" and the user adds > additional templates. I thought we decided against that. But I see your point > that with your logic the users will get to benefit from added templates. > > In my version (you can edit and save with the existing name) the number of > templates shown doesn't go up. And I wonder how often and significantly we'll > change the shipped templates. And in either case, the change doesn't magically > get merged into the modifications... so I think I like mine better. > > The shipped templates stay where they are and don't get overwritten. If the > user edits one of the templates, then the modified template is written into > <systemdefaultdir>/pinting_templates/<same template name> by default, > but the user can opt to pick a different name. > > If the user keeps the name, this is the template they see instead of the > shipped template of that name. So the template loading logic needs to > be modified to FIRST look at the <systemdefaultdir> location, and then > at the others if there's no such file there. > > Makes sense? >
it does and i will attempt it. lubomir -- _______________________________________________ subsurface mailing list [email protected] http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
