Opened 3 years ago
Closed 3 years ago
#22479 closed defect (needinfo)
Changed image sequences can no longer be saved
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Core | Version: | |
Keywords: | template_report | Cc: |
Description (last modified by )
There is no longer a menu item for saving image strings.
Geänderte Bildfolgen lassen sich nicht mehr speichern:
Es gibt keinen Menüeintrag zum Speichern von Bildfolgen mehr.
Attachments (0)
Change History (6)
comment:1 by , 3 years ago
comment:2 by , 3 years ago
The translation is that there is no menu entry anymore to save changed images sequences.
I guess this refers to geoimage layers. Was there something removed? ("Edit images sequence" is still a translatable string.)
comment:3 by , 3 years ago
That makes more sense. The translation I got was
Changed image sequences can no longer be saved
There is no longer a menu item for saving image strings.
Anyway, EditImagesSequenceAction
is only added if the user has Expert Mode
enabled, but now that I have a better idea of what the user was trying to say, I think the user might be missing the photo_geotagging
plugin (Write coordinates to image header
).
comment:4 by , 3 years ago
Owner: | changed from | to
---|---|
Status: | new → needinfo |
comment:5 by , 3 years ago
Description: | modified (diff) |
---|---|
Summary: | Geänderte Bildfolgen lassen sich nicht mehr speichern → Changed image sequences can no longer be saved |
comment:6 by , 3 years ago
Resolution: | → needinfo |
---|---|
Status: | needinfo → closed |
Thanks for your report, however your ticket is incomplete and therefore not helpful in its current form.
Please add all needed information according to this list:
To ensure that all technical relevant information is contained, create new tickets by clicking in JOSMs Main Menu on Help →
Report Bug.
Remember: This is a generic notice so we don't need to write the same stuff again and again. It may only apply in parts to the specific case!
I don't speak or read your language, and the machine translation of your issue was not useful -- I have no clue what feature is the problem.
Please (a) provide a status report and (b) give better steps to reproduce.