Hallöchen! I'd like to start bainstorming about some things that are sub-optimal in Lensfun currently and should be addressed in the next releases. I deliberately do not suggest how to solve them. However, you may also discuss possible implementations.
I post the topics in different messages to make the discussion easier. Okay, the following is the first issue. Let's start with the toughest one: Lensfun makes no distinction between lens and calibration. This means that we may have one lens multiple times in the database. While we can certainly deal with that (it is only unelegant), 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! Yesterday, I added data to the database submitted by a user, which absurdly enough meant that he lost vignetting correction for his lens (which he had before). This must not happen. Tschö, Torsten. -- Torsten Bronger Jabber ID: [email protected] or http://bronger-jmp.appspot.com ------------------------------------------------------------------------------ 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
