[prev in list] [next in list] [prev in thread] [next in thread]
List: amarok-bugs-dist
Subject: [amarok] [Bug 334125] New: lastplay:dd/mm/yyyy filters incorrectly
From: robert marshall <robert () capuchin ! co ! uk>
Date: 2014-04-30 10:12:26
Message-ID: bug-334125-71684 () http ! bugs ! kde ! org/
[Download RAW message or body]
https://bugs.kde.org/show_bug.cgi?id=334125
Bug ID: 334125
Summary: lastplay:dd/mm/yyyy filters incorrectly
Classification: Unclassified
Product: amarok
Version: 2.8-git
Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Collection Browser
Assignee: amarok-bugs-dist@kde.org
Reporter: robert@capuchin.co.uk
If I filter my collection on (for example) lastplay:26/04/2014 I'd expect to
only see tracks I played on that date but I'm seeing lots of tracks I played on
25/05/2014. I think what's happening is that it takes 24 hours from the current
time, so if I filter at 10am I get all the tracks I lastplayed between 10:01 on
25/05 to 10:00 on 26/04?
Maybe this behaviour is as intended and the mapping of the exact date to a time
interval gives unexpected edge cases? I was out nearly all day on 26th so I
wouldn't expect much listening but both lastplay:26/04/2014 and
lastplay:27/04/2014 return lots of tracks so maybe my above diagnosis is wrong
and something else is happening.
If I filter on 30/04/2014 (today) I get tracks I've played earlier as well as
some of yesterdays; If I filter on 01/05/204 (tomorrow) I get tracks I've
listened to today, *all* of which are also included in the 30/04/2014 filter
(which seems very odd to me)
Reproducible: Always
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Amarok-bugs-dist mailing list
Amarok-bugs-dist@kde.org
https://mail.kde.org/mailman/listinfo/amarok-bugs-dist
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic