Re: "F Number" vs. "Aperture Value"

Johannes Zarl-Zierl <[email protected]> Wed, 04 Dec 2019 00:56:28 +0100
Newsgroups gmane.comp.kde.kimdaba
Message-ID <2087187.i3yI1mFjN6@mani>
I've gone forward with removing the GUI item for the search:
https://commits.kde.org/kphotoalbum/8493533368e0a02e88c06f98e3448de45d97d873

I don't have any resources available right now to look into a search by 
brightness, though. If somebody wants to implement something like this, I'm 
not opposed...

Cheers,
  Johannes


Am Dienstag, 3. Dezember 2019, 00:26:57 CET schrieb Johannes Zarl-Zierl:
> Am Montag, 2. Dezember 2019, 23:54:23 CET schrieb Robert Krawitz:
> > I'd definitely have use for finding all photos shot at a given EV
> > value (or range thereof).  That would, however, be an incompatible
> > change and would require rescanning EXIF data, so it's not something
> > we want to do lightly.  But it really isn't clear to me what use I'd
> > have for the APEX aperture value by itself.
> 
> In that case I guess it's best to rename the f-number label as proposed, but
> remove the APEX aperture value from the interface.
> 
> If we really want though, we can get EV values: Adding the required fields
> to compute EV values to the exif database can be done similarly as the gps
> data in a way that doesn't occur a cost to people that don't use the
> feature.
> 
> Cheers,
>   Johannes
> 
> 
> _______________________________________________
> KPhotoAlbum mailing list
> [email protected]
> https://mail.kdab.com/mailman/listinfo/kphotoalbum