para...@paraf.in (2019-Jun-10, excerpt): > Another approach is to add exceptions for specific iops, but that’s > ugly IMHO.
I've implemented exceptions for modules 2 (orientation and highlight reconstruction) and 3 (white balance), added a checkbox, and added the default setting to `darktableconfig.xml.in`. I think it is a valid temporary solution, which can be easily reverted to the more sane approach when (if) the history records all active modules. I'm not sure this is correct. If I get some positive code review, I'd also add documentation, and then issue a pull request... ____________________ [1] https://github.com/darktable-org/darktable/compare/master...s5k6:compressHistory -- http://stefan-klinger.de o/X I prefer receiving plain text messages, not exceeding 32kB. /\/ \ ___________________________________________________________________________ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
