[KPhotoAlbum] gps search: a patch
Reimar.Imhof at netcologne.de
Wed Jun 3 19:41:52 CEST 2015
if we wanted Option 2 (update on startup) it needed to include a question "Do
you want to prepare for gps search? It could take some time." (or something
About option 1: How about a progress bar with cancel button? After pressing
cancel there could be an info about the implicit gps preparation saying
searching will be fast if not searching for gps position info and searching
will be fast again after the first gps search has been done.
To option 3: The automatic exiv update is already (kphotoalbum 4.6.2)
triggered when opening the annotation dialog. It just deals with the shown
pictures and does not convert the exiv info for all pictures.
What about an option 4: Have a new checkbox in the kphotoalbum options dialog
"enable gps search". When doing so it could ask if the gps info should be
converted because it's time consuming. Option 2 and 4 could be combined.
Perhaps option 1 (progress bar with cancel button) could also be useful if a
search process just takes a little more time. For example on my machine the
first gps search costs about 2 seconds. When I've taken more pictures those 2
seconds will become 3, 4 or 5 seconds. And that's to long for a program not
showing any response.
I'd like to have a progress bar (including cacnel option).
What do you think?
I'd prefer an gps yes/no choice in the kphotoalbum option dialog
Am Montag, 1. Juni 2015, 22:45:50 schrieb Johannes Zarl-Zierl:
> > 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
> > or
> > - 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
> KPhotoAlbum mailing list
> KPhotoAlbum at mail.kdab.com
More information about the KPhotoAlbum