|
Side effects of custom sort tag with alphabetical grouping
|
|
22-11-2025, 13:15
Post: #1
|
|||
|
|||
|
Side effects of custom sort tag with alphabetical grouping
Hello,
I've noticed strange behavior when using alphabetical grouping for an indexTag with a custom sort associated with it.
I made test for Schumann works: example:
Instead of finding this work in group "V", I find it in group "#" with all the other Schumann works having the label Work_sort (therefore starting with the same prefix): what does this group correspond to? Does the symbol # represent a number? I have two albums containing this work; on one, it appears on a single track; on the other, it is spread across six tracks. By adding the letter "Z" to the first position of the Work_Sort label on the first album (single track), I find the work in its correct group "V" and no longer in the group "#", even though the tracks on the second album have a Work_Sort label starting with "08". I've noticed another problem: if I specify alphagroup="all", the indextags are correctly grouped alphabetically, except for Work_Rated:Work; omitting the alias doesn't change anything; I think this is another side effect of the Work_Sort tag. thanks in advance for advice |
|||
|
« Next Oldest | Next Newest »
|
| Messages In This Thread |
|
Side effects of custom sort tag with alphabetical grouping - eseb63 - 22-11-2025 13:15
RE: Side effects of custom sort tag with alphabetical grouping - simoncn - 22-11-2025, 21:52
RE: Side effects of custom sort tag with alphabetical grouping - simoncn - 25-11-2025, 11:40
RE: Side effects of custom sort tag with alphabetical grouping - eseb63 - 14-12-2025, 15:30
RE: Side effects of custom sort tag with alphabetical grouping - simoncn - 14-12-2025, 15:44
RE: Side effects of custom sort tag with alphabetical grouping - eseb63 - 16-12-2025, 15:21
RE: Side effects of custom sort tag with alphabetical grouping - simoncn - 16-12-2025, 16:28
|
User(s) browsing this thread: 1 Guest(s)

Search
Member List
Calendar
Help



