Appearance manager

[Old Dog]

Thanks sub!

I'll take a moment and expand on AM's current capability...

Button sets each have their own directory. AM requires two images, a normal main menu button and one selected. AM makes no other restriction. The skin designer can put anything in there, other buttons, selection bars, and headers, whatever.

When the button set is selected, all the files in the set's directory are copied to the skin's top directory. (having said that, it might only copy .pngs but that can be fixed)

[Old Dog]

An interesting thought...

Include a BaseSkin.xml file in the button set's directory, then you could redefine fonts for use with different buttons and headers and such.

[dottore]

you wouldn't have to copy image-files, since it's described in the baseskin, which to use. AND: a skin could have both menus, the vertical and the horizontal.

[Old Dog]

Be advised...

the current public version of AM only copies .png files (see above a couple posts), but that has been fixed for the next release.

[Old Dog]

you wouldn't have to copy image-files, since it's described in the baseskin, which to use. AND: a skin could have both menus, the vertical and the horizontal.

i think it would be better to have different "baseskin"-files, this would give more flexibility.

So that's where this random thought came from...