ok, another Sunday went near the pc, instead of the sea with the family, while all users just have to download and watch
Now I think I'll stop for a while, I need to finish other things in peace.
if you have any reports go ahead, I checked all the files, and I think it works better and more pleasant now.
PREAMBLE:
It is a skin that my friend
@DrAgOn@ passed to me but it had a thousand errors, already at my half-developer sight (not everything

),
I found things that were not at all good for a skin.
It has now been split into multiple xml files, so it's better to work, and not mess all in one file.
Of course I had to redo all the option files in the skinAll folder
QUESTION
The developers of the images should be told to insert a command in the menu, a debug that activates and deactivates, that inserts a label in each screen or xml file that contains them, so that it is easier for skinners to find the screen where they are working . What the fuck does it take to make an on / off button that activates a debug label and writes as an example.
Eg.:
xSkin-0001 == name_file.xml-number_Screen
what I already do with the mMark program, piconsupdater, it takes 1 second for 5 mb of file
I don't think it takes long
