Hallöchen! Russell Edwards writes:
> [...] > > For me there needs to be more feedback to the user, so that they > *can* observe what's happening > > 1) display both the string reported by exiv2 and the string from > lensfun it loosely matches I can understand the desire for input in case something doesn't work out of the box with the Lens module. But what you suggest would be displaying debugging data in my opinion. > 2) display the correction parameters so that they can see they're > nonzero or even modify them manually (I know that's been rejected > before) Has it? It surely is difficult to implement without cluttering up. > Strict rules wouldn't great- I have one that only matches because > of the loose matching rules. If you went that way, it would be > good to have a local aliasing system so you only have to educate > it once about your lens. I think the LensFun DB should be consequently normalized to exiv2 names. If this still leads to ambiguities for whatever reason, duplicate the <lens> entries. But this must be done manually, carefully. No automatic guesswork. Tschö, Torsten. -- Torsten Bronger Jabber ID: [email protected] or http://bronger-jmp.appspot.com ------------------------------------------------------------------------------ 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 [email protected] https://lists.sourceforge.net/lists/listinfo/darktable-users
