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
remaining..
thanks!
On Sat, May 9, 2015 at 9:18 AM, Tony Moore <tonywm...@gmail.com> wrote:
> 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 Ellinghaus" <h...@gmx.de> wrote:
>
>> 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 history entries,
>> or
>> are they just above the selected entry (i.e., 0 - original) and thus not
>> active?
>>
>> > Tony
>>
>> Tobias
>>
>> [...]
>>
>> PS: Please reply to the list and not me personally.
>
>
--
Tony Moore
tonywm...@gmail.com
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
darktable-devel mailing list
darktable-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/darktable-devel
