Adjust timestamp by moving between events
Submitted by an unknown user
Link to original bug (#716185)
Description
---- Reported by shotwell-maint@gnome.bugs 2010-05-15 10:27:00 -0700 ----
Original Redmine bug id: 1925
Original URL: http://redmine.yorba.org/issues/1925
Searchable id: yorba-bug-1925
Original author: Neil Emms
Original description:
It would be a really simple way to fix timestamp data on photos if you could drag the photo to a different event and it would pick up the timestamp from that event and adjust metadata accordingly.
Or, if not, at least let the photo be dragged into the event without affecting the event's current date settings.
I mention this because I dragged a picture without timestamp data into an event containing 15 photos and the entire event moved to Jan 1970, meaning that the one photo without timestamp overrode the 15 correctly stamped photos, which isn't ideal!
---- Additional Comments From shotwell-maint@gnome.bugs 2013-05-01 11:47:00 -0700 ----
History
Comment 1
Updated by Adam Dingle over 3 years ago
- Status changed from Open to 5
- Resolution set to duplicate
- % Done set to 100
neilemms,
Thanks for the bug report. You're absolutely right that in Shotwell 0.5 a picture without a timestamp will cause the entire event to move to January 1970 (or December 1969, depending on your timezone). This is a duplicate of#1152, which has been fixed in the trunk, so this bug will no longer be present in 0.6.
Comment 2
Updated by Charles Lindsay 7 months ago
- Status changed from 5 to Duplicate
--- Bug imported by chaz@yorba.org 2013-11-25 21:44 UTC ---
This bug was previously known as bug 1925 at http://redmine.yorba.org/show_bug.cgi?id=1925
Unknown Component Using default product and component set in Parameters Unknown version " in product shotwell. Setting version to "!unspecified". Unknown milestone "unknown in product shotwell. Setting to default milestone for this product, "---". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Resolution: RESOLVED DUPLICATE