Reply to thread

Message

<blockquote data-quote="Dadeo" data-source="post: 801450" data-attributes="member: 27204">Yeah geichel, I know the experience of hunting through xmls and pulling my hair out <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink&nbsp; &nbsp; ;)" loading="lazy" data-shortname=";)" />Since you are interested, the list widths are set in references.xml - which is basically a default settings file for skin controls.&nbsp; So the main list width is set in the default list control.&nbsp; However, many skin xmls reference a separate file for the facade layouts. In the case of music, it uses common.facade.music.xml (in mymusicgenres.xml you find an import control for common.facade.music.xml). So you could always just add a &lt;width&gt; tag to the list control there.&nbsp; You will notice in aMPed the list control in common.facade.music.xml does not have a width tag - in MP if the tag does not exist it falls back to the default settings in references.xml.&nbsp; That is how aMPed adjusts for screen/font sizes - there is a different references.xml in the Fonts folder for each screen/font size with different default settings (or in many cases styles).&nbsp; So in the main skin xmls aMPed contains very little - instead it uses global settings in references.xml.&nbsp; So if you set a list width/tag in common.facade.music.xml, it would override the list width settings you can select in aMPed Config but then you would get the same list width in music no matter what screen/font size you select and you lose the options.My ultimate goal for aMPed is to make it as 'user-definable' as possible without needing to edit xmls.&nbsp; I plan to add a theme editor and layout selection in aMped 3.4 - if I can find the time!&nbsp; There are always so many updates in MP and plugins it is almost a full time job keeping up, let alone developing new skin features.&nbsp; But I keep trying to add a bit more each version.</blockquote>

[QUOTE="Dadeo, post: 801450, member: 27204"] Yeah geichel, I know the experience of hunting through xmls and pulling my hair out ;) Since you are interested, the list widths are set in references.xml - which is basically a default settings file for skin controls. So the main list width is set in the default list control. However, many skin xmls reference a separate file for the facade layouts. In the case of music, it uses common.facade.music.xml (in mymusicgenres.xml you find an import control for common.facade.music.xml). So you could always just add a <width> tag to the list control there. You will notice in aMPed the list control in common.facade.music.xml does not have a width tag - in MP if the tag does not exist it falls back to the default settings in references.xml. That is how aMPed adjusts for screen/font sizes - there is a different references.xml in the Fonts folder for each screen/font size with different default settings (or in many cases styles). So in the main skin xmls aMPed contains very little - instead it uses global settings in references.xml. So if you set a list width/tag in common.facade.music.xml, it would override the list width settings you can select in aMPed Config but then you would get the same list width in music no matter what screen/font size you select and you lose the options. My ultimate goal for aMPed is to make it as 'user-definable' as possible without needing to edit xmls. I plan to add a theme editor and layout selection in aMped 3.4 - if I can find the time! There are always so many updates in MP and plugins it is almost a full time job keeping up, let alone developing new skin features. But I keep trying to add a bit more each version. [/QUOTE]

Verification