Hi, I tried to make the GUI behavior a little bit more consistent and avoid "hidden" corrections with potentially wrong correction data.
A lens correction is now only applied if there is a full match of camera and lens found in the database or if the user has manually selected a lens - potentially after having selected a camera. There's a clear sign if a lens correction data was found or manually selected: only in this case the three comboboxes for focal length, f-number and distance to object are shown. In a later version of darktable - after the current string freeze - we should give a more explicit feedback to the user like "camera/lens autodetection failed: select manually" or the like. This text would be shown instead of the three comboboxes, so there would be no additional clutter of the GUI. I also opted to go for a strict database search instead of the loose search applied before. Torstens arguments were convincing to me. If the database has ambiguous camera or lens names, not fitting to exiv2 results, it should be fixed. In my opinion it is better to have no lens correction applied, than one with wrong parameters, which goes unnoticed by the user. Please check it and give me feedback, especially if things still do not work as expected. Ulrich ------------------------------------------------------------------------------ Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev _______________________________________________ Darktable-users mailing list Darktable-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/darktable-users
