Am 11.06.19 um 21:26 schrieb Patrick Shanahan:
* Julian Rickards <julian.ricka...@gmail.com> [06-11-19 14:54]:
I must say that I've never used the Compress History option in the
Lighttable, just in the Darkroom. Are there any differences?
On Tue, Jun 11, 2019 at 1:01 PM jys <junkyardspar...@yepmail.net> wrote:
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
___________________________________________________________________________
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
one would *reasonably* expect that they did the same.
AFAIK you are using current master.....
What do you think about just trying it out?
Maybe you'll find a new feature :-)
___________________________________________________________________________
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
