Reply to thread

Message

<blockquote data-quote="RoChess" data-source="post: 975935" data-attributes="member: 18896">Skin files are 'somewhat' easy to understand.&nbsp;They either work by themselves and possibly refer to custom artwork via &lt;texture&gt;....&lt;/texture&gt; (these images are located inside the skins &quot;Media&quot; folder and might therefore need copying as well)&nbsp;Or they rely on other skin files, which are loaded via &lt;import&gt;....&lt;/import&gt;. These are the most dangerous ones to mess with, because the default skin might have a modified version of say &quot;common.dialog.xml&quot;, which you would then need to copy over as well from the default skin folder to the active one and overwrite the one in place, but this could then in turn screw up the entire look of your active skin. Then it is best to wait for your skin developer to find the time to do it properly.&nbsp;You can open the XML skin files with notepad and use CTRL+F to find out on the larger ones, or simply copy the file in place and see if it works.&nbsp;Keep in mind that you will be mixing two totally different skin styles so it might look ugly, but at least it will be functional until the skin developer gets to it.&nbsp;If you are daring you could copy the entire default skin folder content into your active skin folder and tell it to skip any existing files. That way any missing skin file, media file or anything else will be automatically copied into place (advicable to keep a backup of your active skin folder or keep track of what files get 'added').</blockquote>

[QUOTE="RoChess, post: 975935, member: 18896"] Skin files are 'somewhat' easy to understand. They either work by themselves and possibly refer to custom artwork via <texture>....</texture> (these images are located inside the skins "Media" folder and might therefore need copying as well) Or they rely on other skin files, which are loaded via <import>....</import>. These are the most dangerous ones to mess with, because the default skin might have a modified version of say "common.dialog.xml", which you would then need to copy over as well from the default skin folder to the active one and overwrite the one in place, but this could then in turn screw up the entire look of your active skin. Then it is best to wait for your skin developer to find the time to do it properly. You can open the XML skin files with notepad and use CTRL+F to find out on the larger ones, or simply copy the file in place and see if it works. Keep in mind that you will be mixing two totally different skin styles so it might look ugly, but at least it will be functional until the skin developer gets to it. If you are daring you could copy the entire default skin folder content into your active skin folder and tell it to skip any existing files. That way any missing skin file, media file or anything else will be automatically copied into place (advicable to keep a backup of your active skin folder or keep track of what files get 'added'). [/QUOTE]

Verification