[Pete Williams]

Hi

I have been going through the tutorials, and have a question. I have the full version of the library.

My app is a single document app. Forms are opened as child windows onto a main form, and then these are swapped around.

Should I have a TsSkinManager control on each of the child windows? If so, do you set the current skin each time the form is instantiated? It seems to be working with just one.

I am using XE5 if that matters.

Alpha skins is really good by the way.

Thanks

[DarrenB]

'Pete wrote:

Hi

I have been going through the tutorials, and have a question. I have the full version of the library.

My app is a single document app. Forms are opened as child windows onto a main form, and then these are swapped around.

Should I have a TsSkinManager control on each of the child windows? If so, do you set the current skin each time the form is instantiated? It seems to be working with just one.

I am using XE5 if that matters.

Alpha skins is really good by the way.

Thanks

Place a skinmanager on your main form, and a skin provider on each of the other forms. Specify the skin name on your skinmanager and all the 'child' forms will inherit those settings. Skin Provider is recommended because it speeds the drawing process up.

It's also possible to place one or more skin managers on your main form… if you look in the controls for alphaskins, you'll see that under Skindata property, you can 'point' them to different skin managers… the possibilities are huge!

Good luck with whatever you're doing 🙂

Regards

Darren

P.S. I usually get these things wrong but as far as I'm aware the above is correct !

[Pete Williams]

Darren,

Thanks a lot. I've done exactly what you suggested.

The skin provider in on an ancestor, and the skin manager is opened onto an invisible window when the app starts. Each provider references the Manager component directly.

To noobs like me: do this early. It's the right way to go, but I had to change some code part-way through.

[Author]

Posts