INTERACT FORUM
More => Old Versions => JRiver Media Center 26 for Windows => Topic started by: Antoine. on February 22, 2020, 12:04:50 pm
-
When sorting by number of plays, make no data in this field be treated as a value of 0. Right now, if I'm sorting by increasing order of plays, I get files with 1 view first, and files with 0 view at the very end of the list, after the files with most views. Done
-
When sorting by number of plays, make no data in this field be treated as a value of 0. Right now, if I'm sorting by increasing order of plays, I get files with 1 view first, and files with 0 view at the very end of the list, after the files with most views.
What do you have set in "Options > Tree & View > Sorting > Sort empty strings last"
While [Number Plays] is an Integer not a String, that setting seems to affect the sort anyway.
Also read "Field Values: Empty, 0, and 1" in https://wiki.jriver.com/index.php/Expression_Language
-
What do you have set in "Options > Tree & View > Sorting > Sort empty strings last"
It was checked! After I unchecked: the empty values are treated as "0" and my playlist by increasing order of number of plays now makes sense.
But now, If I want another playlist with sorting by decreasing order of number of plays (popular files), all the files with an empty value in the Number of plays are placed first, which makes no sense. So this option does not appear to be a substitute to an empty value in "number of plays" field being treated as a value of 0 view. Sure I can exclude the files with 0 play from the playlist, but it's only a fix.
-
You are correct.
Turning that setting off just seems to sort empty values to the beginning all the time. Empty values should probably be treated as a value of Zero, as per the Wiki.
-
This turned into kind of a long discussion, but I thought I could mention that I noticed some strange behavior, and made this fix to a recent build:
Fixed: Sorting of number style lists would not treat empty elements as zero properly.
Cheers.
-
Thanks for the update Matt. I saw the change and thought it would have been driven by this thread.