For bitmap skins, its possible to indicate the skin is designed specifically for multi-line display. In that case no height adjustment is applied and the user cannot change to single line.
Thats unless you force a specific panel height which it sounds like you are doing.
Also I just discovered that "PlayerMultilineYAdj" is implemented
(https://i.imgur.com/8JordBq.png)
My skin gets it's height enlarged while that shouldn't be necessary considering the height being large enough for that font size.
(the initial panel size is even taller than MB's player panel on the right)
The blue lines indicate the actual background.png size, which is 60px.
The red lines show the enlargement that MB applies.
<element id="PlayerMultilineNoHeightAdjustment">true</element>
1.the font is based on the font the user has set for the player controls panel, and the second line reduces that font size by 0.75 points for the default font and 1.5 points when a custom font is used eg. line 1 is 9.75 points then line 2 is 9 points
What panel element is MB looking for to decide on the font size?
Is it 'panel' or is it 'trackinfopanel'?
If it is 'panel', does it anticipate/guess on a progressbar height?
If it is 'trackinfopanel', my impression is that it may not be making the most of the available space?
2.its historical and was done for Alumni's skins before more general support was added - his skins were specifically designed for 2 line display
After all this testing, I have come to doubt the usefulness and purpose of the: multiLine="true" option that can be set in skin.xml
What is it added value?
It will set (force) multiline by default, and it removes the multiline yes/no option for the user.
But if the user is not thrown off or confused by the absence of the 'disable multiline' option, he can simply empty the value for the second line.
The result would be the same as when the user would have had the option to disable multiline to begin with?
So what is the actual advantage—for either the skinner or the end-user—to use that option in skin.xml?