Composer sorting and reverseName

[simoncn]

(31-03-2015 16:57)baymike Wrote:  Hi Simon,

My first post as an extremely satisfied user of minimserver.

I recently noticed a different behaviour of my settings of tagOptions and tagValues for reversing composer names:

I set up all the options as suggested in the manual, (populationg ComposerSort and so on). However, for a few days the reversing did not work anymore. Also the Lumin app showed for example [Bruckner, Anton] as separate entries for [Anton] and [Bruckner]. I suspect the Lumin app treats the comma as separator for values.
Just now I tried and changed the tagOption entry from "ComposerSort.reverseName.display.index" to "Composer.reverseName.display.index", leaving the tagValues as before at "Composer.value.sort={ComposerSort}, Composer.default={ComposerSort}" and the composer name reversing works again.

Can you confirm this behaviour?

Michael

Thanks very much for pointing out this problem. My apologies for the long delay in replying.

I have checked the User guide and the code and I can confirm that the code doesn't match the User guide description. This is because of an incorrect change to the code that was introduced in update 53.

This incorrect change will be reversed in the next MinimServer update and you will need to change your settings to match the User guide description. I have added some text in the last two paragraphs of this section explaining the new rules for how this works.

In the example that you followed when doing your tagging, it is important not to apply the reverseName setting to the Composer tag because the point of the example is that Composer tags contain values that would not be reversed correctly. Applying the reverseName setting to the ComposerSort tag is OK because these values will be reversed correctly.