Am 26.02.2015 um 08:01 schrieb Torsten Bronger: >>> Let's start with the toughest one: Lensfun makes no distinction >>> between lens and calibration. [...] Lensfun is currently unable >>> to take calibration data from different calibration entries for >>> one lens. This means that in a lot of cases, data is there but >>> cannot be used! [...] >> >> Good point, this really is a problem. What about a solution >> similar to this? http://sourceforge.net/p/lensfun/features/19/ > > Yes, I think this is the way to go. > > But the second part of this issue is, how do we realise it in the > code?
To be honest, I currently do not have a complete overview of the database code so I could not even suggest where to start working on this. And I fear I also won't have the time to implement such a feature in the near future. But we should at least create a Wiki Page or Bug to take track of the ideas for a new database format. Same for the alias issue. Sebastian ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Lensfun-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lensfun-users
