[SzakiLaci]

Hi,

Sorry, but I don't really understand what I've found at the FAQ:

Quote:

What do I need the TsSkinProvider item for?

The item is used to skin a form, menus, standard and 3rd-party controls located on this form. It means the itemshould be dropped on every form the layout of which is compliant with skin. The result of the item performance can be only seen in run-time, in design-time the form has a standard kind.

I have 1 of it on the Main Form only, and the program works well!

Do I really need to put 1-1 of that on EACH form? (If yes, can it be somehow automated?)

Thanks 😉

[Support]

Placing of the TsSkinProvider in design-time is recommended.

This component is created in any case, but if this component created by developer in design-time, then he can change a skinning properties of the form, and some things (like animation under Aero) works better.

[Support]

Placing of the TsSkinProvider in design-time is recommended only.

This component is created in any case, but if this component created by developer in design-time, then he can change a skinning properties of the form, and some things (like animation under Aero) works better.

[Colin]

Not sure if I should add to this old thread, but I've found an exception to this rule that may be helpful to users of Billenium Effects 4. I'm using v4.4 beta 2 with DXE2 and found that I can not include a TsSkinProvider on the form if I want the transitions to work at all. I'm using the BE form transition effects rather sparingly so removing the TsSkinProvider from a small number of forms didn't seem to affect the performance of the skinning features, in my case, as far as I can tell.

Colin

[Author]

Posts