Make HTags saved search behavior consistent with add/modify tags dialogs
Submitted by Lucas Beeler
Assigned to Lucas Beeler
Link to original bug (#718041)
Description
---- Reported by lucas@yorba.org 2011-08-20 16:52:00 -0700 ----
Original Redmine bug id: 4005
Original URL: http://redmine.yorba.org/issues/4005
Searchable id: yorba-bug-4005
Original author: Lucas Beeler
Original description:
You can use a slash character to specify hierarchical tag partial paths in the saved search dialog box (e.g. "animals/dogs") but you can't use the slash character in the add/modify tags dialog boxes.
For 0.11, the behavior of the add/modify tags dialogs is correct and the behavior of the saved search dialog is incorrect (we've intentionally disallowed partial path specification to simplify for 0.11). The fact that the saved search behavior is incorrect is due to an oversight in the way that indexable keywords are generated. This should be fixed before 0.11 ships.
Just to be clear though: versions of Shotwell after 0.11 will allow partial path specification and path disambiguation (see #3911 (closed) and #3912). We just need to think a little more about how this works in general and especially how it works with autocomplete.
Related issues: precedes shotwell - 3912: Make saved searches fully hierarchical tags- aware (Open)
---- Additional Comments From shotwell-maint@gnome.bugs 2013-05-01 11:38:00 -0700 ----
History
Comment 1
Updated by Lucas Beeler over 2 years ago
- Description updated (diff)
Comment 2
Updated by Lucas Beeler over 2 years ago
- Status changed from Open to 5
- Resolution set to fixed
Fixed in 05df37d1
Comment 3
Updated by Charles Lindsay 7 months ago
- Status changed from 5 to Fixed
--- Bug imported by chaz@yorba.org 2013-11-25 21:55 UTC ---
This bug was previously known as bug 4005 at http://redmine.yorba.org/show_bug.cgi?id=4005
Unknown Component Using default product and component set in Parameters 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.
Version: 0.11
Resolution: RESOLVED FIXED