On Tue, Jun 11, 2019, at 07:47, thokster wrote: > Is the "compress history" button in lighttable view doing anything else? > If you use this button you can clean up all selected pictures with one > click (incurrent master). > I probably totally misunderstood what you were up to.
The current implementation of "compress history" only removes duplicate entries per each module. The idea here is to also remove single instances of modules which are set to "(off)". I think it would be good to get some broader feedback about how to best implement this, since this is an area where workflows might vary greatly, and sometimes it's hard to think outside your own. Personally, I can think of times when an operation to remove these would be useful, but maybe not always in conjunction with "normal" history comression. They seem like two slightly different cleanup operations to me, for whatever that's worth. -- jys ___________________________________________________________________________ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
