|
|
Displaying the total number of plays of an album or group of songs can be valuable, but if editing the value applies the same number to each song, that is logically inconsistent. Perhaps we can split it into two fields: Play counter, which shows the played # of each individual track; and Play total, which shows the total played # of all the selected files. The latter should only appear if multiple files are selected. This way, we can make Play counter behave the same as all other fields (Show a number if all selected tracks share the same value; leave empty otherwise); while still showing the total played # for all selected songs. If we do this, we might like to consider swapping the rows for Track/Album volume with Play/Skip counter, so that we stay visually consistent with the optional Bookmark row (keeping optional rows at the bottom) while keeping the Play/Skip rows together. image.png (75,006 bytes) |
|
|
1) I'm not sure that there's much benefit in displaying 'Play total', so I'd go with the originally suggested approach (also discussed at 0019190) of not summing the play counts and having this field work similarly to other fields in the dialog. 2/3) How about when multiple tracks are selected and the field values are empty just show "" (as today), and when field values differ, show a greyed-out "≠" (so that it's clear that this isn't an actual value). |
|
|
I like drakinites idea (re showing play total. Its advantage is because there is a loss of function from MM4 if the sum of selected plays is not displayed where multiple tracks have been selected. If the loss of function is OK, then I like Rusty's 2/3 suggestion re ≠ ... because a blank display, where the selection has mixed values would be very confusing for Play Count. nb. the ≠ idea is important for drakinites proposal also IMO. His diagram shows play count of 1, with a total of 6. So if I had 6 tracks selected, each with a play of 1, then I could increase count t 2, and expect a new total of 12. But if it was just two tracks selected, one with 6 plays, and the other with none, then the same change would result in a decrease of total plays to a sum of 4. I think that the user would need some heads up indication, such as the ≠ symbol, when the transaction is more complex than it appears on the surface |
|
|
I think that introducing 'Play total' doesn't help much here to be clearer as one can hardly understand whether it is track total played# or track selection total played# I guess that the sum was there in the times when Play counter wasn't editable field, but once later the Play counter became editable then showing the sum of Played# is confusing and probably not desired. In true I doubt that everyone understands what the number is and that it is a total sum of all selected tracks. The second question is who cares of the total Played# sum for the tracks selection? I guess this is rather useless info IMO? I would suggest to unify this with other editable fields: i.e. show it empty until all tracks in the selection has same Played# value. |
|
|
Ludek: "In true I doubt that everyone understands what the number is and that it is a total sum of all selected tracks. The second question is who cares of the total Played# sum for the tracks selection? I guess this is rather useless info IMO? I would suggest to unify this with other editable fields: i.e. show it empty until all tracks in the selection has same Played# value." I agree with Ludek's comments, and with his suggestion. . |
|
|
Fixed in 5.1.0.2823 |
|
|
Verified on 2823. Played# shows value when multi-select has same value, no value if multi-select has differing values. |
- Anonymous
