Looks like the ...e1df5c26d1b6 commit fixed it when I reimported the images.
Also, I noticed when in lighttable and I select history stack -> discard
that it points to the top of the history stack including the base curve..
I'll probably try "select untouched" and then "discard" to fix the
remaini
Of course. It seems the id in the image table does not always have a imgid
in the history table so the sql cmd does not affect those images and when
opened in darktable I see there is history 0 to 3 for new images but zero
is the active one. Hope that is clear.
Tony
On May 9, 2015 9:00 AM, "Tobias
Am Samstag, 9. Mai 2015, 07:16:31 schrieb Tony Moore:
> Thanks for the suggestion. It seems there aren't any history entries for
> most of the images I recently imported so I still see the same issue. Hope
> this helps with the debug...
Could you be a bit more precise? Do you positively lack histo
Am Freitag, 8. Mai 2015, 22:27:00 schrieb Tony Moore:
> Is there a lua script that could reset the history stack and point it to
> the top?
No, Lua can't access the database directly. I am currently working on fixing
this bug ( I already got styles to work again), but for the mean time you
could
Am Donnerstag, 30. April 2015, 11:31:36 schrieb Chris Siebenmann:
> As of commit a237fa1ff370c77dfbac1f809a5df32148ea5bbc, 'Preserve
> history above selected when leaving dr', the behavior of Darktable in
> the darkroom is that when you select a new image you're placed on the
> *bottom* of the (de
As of commit a237fa1ff370c77dfbac1f809a5df32148ea5bbc, 'Preserve
history above selected when leaving dr', the behavior of Darktable in
the darkroom is that when you select a new image you're placed on the
*bottom* of the (default) history stack (on 'original'). This leaves
orientation, sharpen, an
