please be accurate. will definitely not implement all the many ways dt has to achieve the same. in particular not if it’s about gui dialogs. (selective copy can be achieved by a temporary preset, has very similar ui to select history entries)
an update will not write to the version in your home, which takes preceedence.
i disagree. on the other hand doing fs_copy in code behind a button instead of copying your example .cfg to the default.<input module> config files isn’t introducing a whole lot of ui complexity and clutter.
now that would be overwriting your stuff upon update. i see how it will make the place of config files more obvious, but the solution doesn’t seem so easy.
i think i agree here.
shows it where? under the histogram or in the metadat expander? there are three sources of common metadata: rawspeed (black/white/matrix), exiv2 (orientation, shutterspeed etc, dng matrices), and exiftool (configurable metadata expander).