instead of deleting darktablerc you can edit it and change the opacity setting for retouch there
> Am 08.12.2021 um 19:15 schrieb I. Ivanov <iv3...@gmail.com>: > > >> On 12/7/21 21:59, Andrew Greig wrote: >>> On 8/12/21 10:32 am, I. Ivanov wrote: >>> >>> On 12/7/21 13:44, Andrew Greig wrote: >>>> How do I set the retouch opacity to default to 100% please? >>> Does it not remember what is last? If I am to change the opacity *before >>> starting the retouching* - it keeps for me what I have selected. >>> ____________________________________________________________________________ >>> >>> darktable user mailing list >>> to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org >>> >> Hi, >> >> It does remember what was last used except that when I had dropped the >> opacity for a single use it seems to set that as a new starting point. So >> when I have restored my need for 100% opacity and finished on 100%, my next >> use will stat at 30% and then I have to scroll up to 100%. >> > Hi Andrew, > > For me it appears to stick to whatever I set it. > > - If I start retouching (at any opacity - say 90) and after that I change the > opacity of the existing shape to 100 - the next retouch will use the 90 as a > starting point (because this is what I started with) but > > - If I first set the opacity (say 100) then each shape I make will be at the > chosen opacity. This also appears to persist between images, between restart > of DT and also between different tools - the opacity set in retouch will > persist in other modules (for example haze removal). Vice versa is also true > - opacity set in another module will carry forward to retouch. > > I am not sure if there is some specifics to os / version etc. but just FYI - > I am on pop OS 20.04, DT 3.6.1 > > It is good that the suggestion from Patrick helps you. But unless there is > something apparent like version, OS etc - I don't know why would it behave > different. > > Sometimes I try backing up (renaming) ~/.config/darktable in order to start > afresh (for a test) but what it would tell me is if there is something that > exists in the config files that triggers the behavior or not. But this would > be mainly to satisfy the curiosity. > > Regards, > > B > >> >> Andrew >> >> ____________________________________________________________________________ >> 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 > ____________________________________________________________________________ darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
