Bug 388219 - Geolocalization: Process to manually set a picture's capture position is undiscoverable
Summary: Geolocalization: Process to manually set a picture's capture position is undi...
Status: REOPENED
Alias: None
Product: digikam
Classification: Applications
Component: Geolocation-Workflow (show other bugs)
Version: 5.8.0
Platform: Microsoft Windows Microsoft Windows
: NOR wishlist
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
: 328855 388221 (view as bug list)
Depends on:
Blocks:
 
Reported: 2017-12-25 16:59 UTC by uwestoehr
Modified: 2024-12-20 21:32 UTC (History)
3 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description uwestoehr 2017-12-25 16:59:15 UTC
I want to set the location of images. Therefore I open a folder in the album view.

Now I right-click on an image.

result: the context menu doesn't provide to set the location

OK, now I try to get the location by dragging it on a map. Therefore I open a map on the left side but then the album view gets empty, see bug 388199.

From the manual I know that the map on the right side cannot be used to change parameters.

After fiddling around for about an hour I found out that I

1. have to select the image
2. need to open the Extras menu on the right side
3. choose on the right side the geolocation editor
4. now in this editor I can drag the image to the map
5. to tag the next image I have to close the geolocation editor because otherwise I cannot select another image from the album view
6. select the other image
7. open the geolocation editor again and drag the image there to the map

I guess I do something wrong but as newbie with the manual as help I cannot find abetter solution. If what I do is the normal workflow it should be improved:

1. right-click on the image
2. choose there in the context menu an entry "set location"
3. this opens the geolocation editor where one can drag the image to the map
4. one clicks on the album view again and the geolocation editor is pushed behind (minimized) to be able to see the full album to select another image
5. right-click on the new image and repeat step 2. and 3.
Comment 1 Maik Qualmann 2017-12-25 18:30:14 UTC
This map only shows an overview of the images with geolocation positions. I think I have to create a screencast for you. For editing is the geolocation editor. Either by Ctrl+Shift+G or in the "Items" menu. Auf Deutsch unter "Eintrag". You can also select multiple images in the Album View. Now you open the geolocation editor. Here you have an image list below the map. Here you can now select individual or all images and drag into the map. So you can also assign the coordinates to 100 images at once.

Maik
Comment 2 uwestoehr 2017-12-25 18:44:29 UTC
> Now you open the geolocation editor. Here you have an image list below the map. Here you can now select individual or all images and drag into the map. So you
> can also assign the coordinates to 100 images at once.

I understood but this issue is about workflow. In all programs I use (LibreOffice, Inkscape etc.) one can right-click on an element to change its properties. in digikam I cannot right-click on an image to set or to change its location. Therefore my proposal in the initial comment of this bug would in my opinion improve the workflow a lot.
Comment 3 Maik Qualmann 2017-12-25 20:06:49 UTC

*** This bug has been marked as a duplicate of bug 328855 ***
Comment 4 caulier.gilles 2022-01-10 15:45:35 UTC
*** Bug 388221 has been marked as a duplicate of this bug. ***
Comment 5 caulier.gilles 2022-01-10 15:46:32 UTC
*** Bug 328855 has been marked as a duplicate of this bug. ***
Comment 6 Philippe Cloutier 2023-10-15 15:40:50 UTC
I'm fixing this ticket's title. A couple comments:
1. This is an ITS. Entries are issue reports, not (directly) requests.
2. The term "workflow" refers to heavy processes. Something as simple as setting an image's location should be is not complex enough to qualify as a "workflow": https://en.wiktionary.org/wiki/workflow
Comment 7 uwestoehr 2024-12-01 23:18:00 UTC
Why was this reopened? This bug is very old, I don't use Digikam anymore, cannot test if it still valid etc. Please leave it closed and open a new bug report if there is still a similar issue in Digikam.
I mean what has not been changed in 7 years is obviously not important and the bug can be closed.
Comment 8 Philippe Cloutier 2024-12-02 01:45:09 UTC
uwestoehr: The RESOLVED status is meant to identify resolved issues. If you no longer use the product and do not know whether the issue is resolved or not, thanks for letting the ticket alone. Others who can test will take care of updating the ticket when needed.
Comment 9 uwestoehr 2024-12-02 17:32:26 UTC
I don't get the rationale: bug was not fixed/addressed for 7 years. so why not closing it and reopen a new one if necessary? Otherwise you just pollute the bug tracker with the effect that new bug reporters but also maintainers/developers have to check a huge amount of bugs.
We do this all in our spare time and I don't see reason why people should be bothered by a bug report that I once made and that is most probably resolved.
And since it is my bug report, I must have a chance to close the report. As I wrote, you can open a new bug report that is then also based on recent Digikam with recent workflow and information.
Thanks.
Comment 10 Philippe Cloutier 2024-12-03 16:03:00 UTC
(In reply to uwestoehr from comment #9)
> I don't get the rationale: bug was not fixed/addressed for 7 years.

This is not a bug.

> so why not closing it and reopen a new one if necessary?

To be closed, the issue tracked by a report must have been resolved.

> Otherwise you just pollute
> the bug tracker with the effect that new bug reporters but also
> maintainers/developers have to check a huge amount of bugs.
> We do this all in our spare time and I don't see reason why people should be
> bothered by a bug report that I once made and that is most probably resolved.

What makes you think that this issue is "most probably resolved"?
Comment 11 uwestoehr 2024-12-16 03:03:54 UTC
Please, I don't want this bug anymore. Open a new bug if the problem still exists so that this bug does not appear anymore in my list. I made a mistake in reporting this issue, OK. But I must have the right to get rid of this somehow.
Comment 12 Philippe Cloutier 2024-12-20 21:32:03 UTC
(In reply to uwestoehr from comment #11)
> Please, I don't want this bug anymore.

This is a request for improvement, not a bug.

> Open a new bug if the problem still
> exists so that this bug does not appear anymore in my list. I made a mistake
> in reporting this issue, OK. But I must have the right to get rid of this
> somehow.

Please:
1. clarify which list you are referring to and which mistake you made
2. stop setting the Status to RESOLVED until you have evidence that the issue is indeed resolved.

You can visit #kde-www for assistance with this site: https://userbase.kde.org/IRC_Channels