For me having disabled modules in history is very useful, because the modules may have some non-default parameters set, and later I may want to re-enable them. For example, I can apply the watermark module, change some colors/position, export with the watermark. Later I can disable the watermark module to export for some other purpose. If I want to export with a watermark again I want it to remember colors/position I set before, even after stack compression.
-Sergii. On Wed, Jan 31, 2018 at 8:48 AM, Harald <mj...@email.de> wrote: > Hi, > > I don't understand why the history stack still contains - or generally > should contain - disabled modules after stack compression. > > I have seen the procedure for cleaning up deselected modules, but it > seems to me to be very complex, especially for multiple deselected > modules within the same stack. > > Unfortunately, I have to disable alternative modules again at a later > stage, due to ongoing module comparisons. > > Would a global function in Lighttable for compressing and deleting > disabled history stack module entries for a group of selected photos be > a useful extension for darktable? > > Any other idea would help to create my own 'clean' styles ... ? > > Thanks and Regards > > Haribo M > > ____________________________________________________________ > ________________ > darktable user mailing list > to unsubscribe send a mail to darktable-user+unsubscribe@ > lists.darktable.org > > ____________________________________________________________________________ darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
