add/modify tags missing in video context menu
Submitted by an unknown user
Assigned to Jim Nelson
Link to original bug (#717198)
Description
---- Reported by shotwell-maint@gnome.bugs 2011-01-07 13:53:00 -0800 ----
Original Redmine bug id: 3075
Original URL: http://redmine.yorba.org/issues/3075
Searchable id: yorba-bug-3075
Original author: Richard B. Kreckel
Original description:
This is a bit missing from the implementation of Ticket #2762 (closed): The context menu of videos doesn't allow to add or modify tags.
Could this please added if a 0.8.1 release is made? The ability to manage photos and movies in the same way is quite important. I know it, because I'm using shotwell with children and most of the time I am really impressed. But the missing tags in the context menu annoyed me enough that I bothered to see how to fix it myself. The attached patch works fine for me.
---- Additional Comments From shotwell-maint@gnome.bugs 2013-05-01 11:39:00 -0700 ----
History
Comment 1
Updated by Adam Dingle almost 3 years ago
-
Priority deleted (
<strike>
__</strike>
)
The patch is tiny, so I think it would be reasonable to include this in 0.8.1 if it all looks fine. Jim, can you review?
Comment 2
Updated by Adam Dingle almost 3 years ago
- Status changed from Open to Review
- Assignee changed from Anonymous to Jim Nelson
Comment 3
Updated by Jim Nelson almost 3 years ago
- Status changed from Review to 5
- Resolution set to fixed
- % Done changed from 0 to 100
r2547
Comment 4
Updated by Charles Lindsay 7 months ago
- Status changed from 5 to Fixed
--- Bug imported by chaz@yorba.org 2013-11-25 21:49 UTC ---
This bug was previously known as bug 3075 at http://redmine.yorba.org/show_bug.cgi?id=3075 Imported an attachment (id=261920)
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 FIXED