This has always been the default behavior. That it will use "overwrite" one time only and then revert to "create unique filenames". However, if I'm not mistaken, version 3 is going to allow you to make it stick to "overwrite" if you want it to.
Cheers, Bruce Williams. ---------- Forwarded message --------- From: Coding Dave <codingd...@gmail.com> Date: Wed., 11 Dec. 2019, 05:13 Subject: Re: [darktable-dev] Export settings, not storing "on conflict" setting To: Cc: darktable <darktable-dev@lists.darktable.org> Hi, I think this is an intentional decision. Julian Rickards <julian.ricka...@gmail.com> schrieb am Di., 10. Dez. 2019, 17:43: > Hi: > > I'm running 2.6.3, I haven't tried any of the dev versions so can someone > check this for me please? > > When I create/edit an Export preset and set the "on conflict" to > "overwrite", it doesn't save this setting but reverts to "create unique > filename". > > Is this "reluctance" to save the "on conflict" to "overwrite" intentional? > If it is a bug, can someone check 3.0 and see if it has been fixed? > > Sorry, just noticed this. > > Not critical, can be left for 3.0.1. > > Thanks, > > Jules > > ___________________________________________________________________________ > darktable developer mailing list to unsubscribe send a mail to > darktable-dev+unsubscr...@lists.darktable.org > ___________________________________________________________________________ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org ___________________________________________________________________________ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
