Bug 182326 - Remember last position when geotagging images
Summary: Remember last position when geotagging images
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Plugin-Generic-GeolocationEdit (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR wishlist
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-29 18:11 UTC by Benjamin Schindler
Modified: 2016-07-20 06:09 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 1.1.0
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Benjamin Schindler 2009-01-29 18:11:47 UTC
Version:           0.2.0-rc1 (using KDE 4.2.0)
Compiler:          gcc-4.3 
OS:                Linux
Installed from:    Gentoo Packages

When geotagging large number of pictures, it is essential for this tool to work efficient

Remembering the last position geotagged (and the zoom level) would help enormously with this.
Comment 1 caulier.gilles 2009-01-29 18:51:39 UTC
Benjamin,

It's already the case if you press on OK to apply GPS position with google map editor...

Gilles Caulier
Comment 2 Benjamin Schindler 2009-01-29 19:55:35 UTC
Hi

I just looked at the code and indeed - it should be there, however, it does not work here

I looked at ~/.kde4/share/config/kipirc and the entried GPH Last Altitude, Latitude and Longitude just stay 0 forever. 
I'm on a releasebuild so I can't really step through the code however I did a strace and at least, kipirc is opened

Comment 3 Michael G. Hansen 2009-11-26 12:31:11 UTC
Benjamin, do you have this problem with kipi-plugins 0.8?

Michael
Comment 4 Michael G. Hansen 2009-12-03 21:54:42 UTC
Benjamin, version 0.9 is now available. Could you test it with this version?

Michael
Comment 5 Michael G. Hansen 2010-01-23 20:46:54 UTC
No reply for more than two month, closing this report.

Michael
Comment 6 caulier.gilles 2015-06-28 10:03:02 UTC
New Kipiplugins 4.11.0 is available :

https://www.digikam.org/node/740

Can you reproduce the problem with this release ?

Gilles Caulier