View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0020038 | MMW 5 | Tagging / organizing (properties / auto-tools) | public | 2023-05-18 11:37 | 2024-02-23 17:21 |
| Reporter | peke | Assigned To | |||
| Priority | high | Severity | tweak | Reproducibility | always |
| Status | closed | Resolution | reopened | ||
| Target Version | 2024.0 | Fixed in Version | 2024.0 | ||
| Summary | 0020038: When Play/skip count is updated from Track properties then Last play date should be too | ||||
| Description | If user update Play/skip count is updated from Track properties then Appropriate date values should be too eg. Play/Skip count updated -> Last play updated | ||||
| Additional Information | https://www.mediamonkey.com/forum/viewtopic.php?p=509963#p509963 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 2824 | ||||
|
|
I am not sure whether this is desired? User might want just to increase (or descrease) play count without updating 'Last Played' / 'Last Skipped' ? |
|
|
User Confirmed that it would make him "Whole" and switch to MM5, I also think that point of updating play counts is to update Last played, including when user wants to delete it an then also play/skip need to be deleted too. Maybe standard dialog with "Would you like to also update Last Play/Skipped date? [ ] Do not ask anymore [Yes][No]" with default on YES? |
|
|
I think it would usually make sense to update last played / last skipped at the time that the user _increases_ the associated count, so we could probably do this without any UI . |
|
|
Fixed in 5.1.0.2822 |
|
|
Added the clearing when set to zero in build 2823 |
|
|
On 2823, verified that when Played# is set to 0 that Last Played is removed. However deleting Played# (instead of inputting 0) does not remove the Played# value, unlike other fields. |
|
|
Fixed in 5.1.0.2824 |
|
|
Verified 2824 |
