Aldric, Seems like there is an issue with the way the multi_priority is set.
Do the following test: $ sqlite3 .config/darktable/library.db On another console launch darktable: Import a new image (jpeg it is easier), say image 816: sqlite> select num,operation,multi_priority,multi_name from history where imgid=816; => nothing that's good In dt, apply exposure (whatever the value) and back to lighttable, then: sqlite> select num,operation,multi_priority,multi_name from history where imgid=816; sqlite> select num,operation,multi_priority,multi_name from history where imgid=816; 0|exposure|0| => looks fine, num=0 with multi_priority 0. Then add a new instance of exposure and back to lighttable, then: sqlite> select num,operation,multi_priority,multi_name from history where imgid=816; 0|exposure|1| 1|exposure|0|1 => this is wrong! The new exposure is marked with multi_version=0 and multi_name=1??? And the previous one got a multi_priority of 1!!! No style involved. I found this issue when looking at the style issue you reported. This needs fixed before I dig further into the style issue. Can you have a look? Pascal. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk _______________________________________________ darktable-devel mailing list darktable-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/darktable-devel
