[KPhotoAlbum] gps search: a patch
johannes at zarl.at
Mon Jun 1 22:45:50 CEST 2015
> To me the one point to deal with is the performance problem when the gps
> access triggers an exiv db update. I mentioned that yesterday. I didn't
> measure that time but it just felt like taking ages.
> I could think about two possibilities:
> - having a search progress bar - meaning the first search including that
> update will take some time
> - convert the exiv db during start up (like looking for new pictures) - so
> the first start up could by time expensive.
For me, neither option is ideal. Option 2 (update on startup) will be quite
frustrating, especially for users who don't use geotagging.
Option 1 is potentially better, but I would prefer it if the user gets a
choice as soon as he/she enables the gps search.
I see at least one other option:
(3) Do not trigger updates to the exiv DB, and ignore missing gps values
A definite upside to option 3 is a low performance overhead. The downside that
should not be understated lies in the potential confusion of the users.
More information about the KPhotoAlbum