(Some) Filters do not Update While in Photo Mode
Submitted by Charles Lindsay
Link to original bug (#719237)
Description
---- Reported by joseph.bylund+shotwell@gmail.com 2013-05-30 16:29:00 -0700 ----
Original Redmine bug id: 7020
Original URL: http://redmine.yorba.org/issues/7020
Searchable id: yorba-bug-7020
Original author: Joe Bylund
Original description:
One possible set of steps to reproduce: In a set rate a few photos 5 star, set the filter to 5 star. Double click a photo to enter photo mode, use arrow keys to loop through photos. Set one of the ratings to 4 (or other), and continue looping through the photos. Note the photo with 4 stars is still included in the selection. I would expect the photo to be removed from the selection when I change the rating (and therefore not come up again). Let me know if that's confusing.
---- Additional Comments From shotwell-maint@gnome.bugs 2013-05-31 15:57:00 -0700 ----
History
Comment 1
Updated by Jim Nelson 6 months ago
- Status changed from Open to Invalid
That makes sense, Joe, and in fact was the original behavior long ago. It turned out it was too confusing for some users, especially when the Rating change (or another filtered criteria) was set by accident. Or, the user isn't sure if it's a 4 or a 5, picked 4, then wants to pick 5, but it's gone.
Also, when the last email is set to 4, the only recourse is to go back to the photo library, which is also kind of unexpected.
That's why I'm marking this Invalid.
--- Bug imported by chaz@yorba.org 2013-11-25 22:11 UTC ---
This bug was previously known as bug 7020 at http://redmine.yorba.org/show_bug.cgi?id=7020
Unknown version " in product shotwell. Setting version to "!unspecified". Unknown milestone "unknown in product shotwell. Setting to default milestone for this product, "---". The original reporter of this bug does not have an account here. Reassigning to the person who moved it here: chaz@yorba.org. Previous reporter was joseph.bylund+shotwell@gmail.com. Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Resolution: RESOLVED INVALID