Having the *default* set to something which would potentially destroy data is never, ever a good idea.
Having the ability to store the "on conflict" -setting, so it would be saved across sessions, to something else than the default, is another matter; that would be good. Kind regards, Kristian On Wed, 1 Jun 2016 at 07:29 thokster <thoks...@gmail.com> wrote: > > +1 > > Am 01.06.2016, 03:09 Uhr, schrieb <darkta...@911networks.com>: > > > On Wed, 1 Jun 2016 07:34:13 +0800 > > Louis Turk <l...@dayspringpublisher.com> wrote: > > > >> Is there any way to make "on conflict" default to "overwrite"? If > >> not, could it be made possible? In my workflow, I never use "create > >> unique file name" intentionally, so having to change to "overwrite" > >> each time I make corrections is time-wasting, especially if I forget > >> and end up having to delete and/or rename a bunch of files. > > > > +1 > > > > BTW, even with a preset, it's not possible to store the "overwrite" > > status, it always comes up as: on conflict: "create unique filename". > > > > If I could store all the export settings (including the on conflict), > > that would be good enough for me. > > > > > > ____________________________________________________________________________ > darktable user mailing list > to unsubscribe send a mail to > darktable-user+unsubscr...@lists.darktable.org > > ____________________________________________________________________________ darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
