Currently, all mounts of a lens need to be taken into account for uniquely identifying a lens. This is because of the compact cameras, for which the lenses are called "Standard". Thus, the combination of maker, model, and cropfactor is not enough to make a <lens> database entry unique.
On the other hand, the need for ALL mounts in the primary database key for lenses is awkward: The calling programs, e.g. Darktable, do not show the mounts to the user, so in the worst case, the users sees two lenses with the same name in the list, and does not know which one to select. In reality, this will happen very rarely, because the probability for two lenses differing only in the mounts is rare. But it is not impossible. Possible solution: Re-name all compact camera lenses to the model name of the *camera*. Possibly this can be translated to English with "Standard", so that the user would not notice the change. Furthermore, document and enforce the convention that the default lens (i.e., no converter, default output format) has the shortest lens model name. Any commens/objections? ------------------------------------------------------------------------------ Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test & Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees _______________________________________________ Lensfun-users mailing list Lensfun-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lensfun-users
