Composer sorting and reverseName

[simoncn]

(09-11-2015 21:41)simoncn Wrote:  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.

This change (in update 71) caused a problem, so I have modified it slightly in update 73. Instead of

tagOptions: ComposerSort.reverseName.display.index
tagValue: Composer.value.sort={ComposerSort}, Composer.default={ComposerSort}

you need to specify

tagOptions: ComposerSort.reverseName.display.index
tagValue: Composer.value.sort={ComposerSort}, Composer.default={ComposerSort.custom}

I have updated the User guide to reflect this change.