DXDesignKeys

Hi

I had set with DXDesignKeys the skin to something others then Caramel.
This works when dropping controls on the a form.

However, when making a new project, with an XtraForm and adding

DevExpress.Skins.SkinManager.EnableFormSkins();
DevExpress.LookAndFeel.LookAndFeelHelper.ForceDefaultLookAndFeelChanged();

to the main routine, the program still startup in the Caramel skin.
In desing time the controls dropped on this form are in the selected skin, but change when running also to caramel.

So still need to add an extra line here to set the right skin.

Seems that DXDesignKeys default only works for controls on a form and not for a form.

Or do I something wrong.

Peter

Hello Peter,

Thank you for the question. I should say that this tool have affect only at design-time. To mage the same skin to work at runtime, you should place the DefaultLookAndFeel component on the main form and adjust its LookAndFeel properties.

Please try this solution and inform us of your results.

Thanks,
Stan.

Hello

Aha, its only a design time tweak. I thought it would also set the runtime to use that skin which was choosen by the program, but i see it switches back to Caramel.

So to have a whole project the same skin i still need to set the skin with

DevExpress.Skins.SkinManager.EnableFormSkins();
DevExpress.LookAndFeel.LookAndFeelHelper.ForceDefaultLookAndFeelChanged();
DevExpress.LookAndFeel.UserLookAndFeel.Default.SkinName = "Black";

Usiing the DefaultLookAndFeel control is not an option as the project has multiple forms.

Btw, when testing i also meantioned that first setting the default skin to another, dropping some controls a form they show the correct skin. But drop a DefaultLookAndFeel on the form all control revert to Caramel. When removing the DefaultLookAndFeel on the form all controls (old and newly added, even on a newlu created form) still get/have the caramel skin again and not the choosen standard. One have to make a new solution to get back to the skin choosen with DXDesignKey.

Peter

Hello Peter,

Thank you for the response. Here are my comments:

>>
Usiing the DefaultLookAndFeel control is not an option as the project has multiple forms.
<<
Actually, the DefaultLookAndFeel component works in the same way as the code your mentioned. It affects an entire application.

>>
Btw, when testing i also meantioned that first setting the default skin to another, dropping some controls a form they show the correct skin. But drop a DefaultLookAndFeel on the form all control revert to Caramel. When removing the DefaultLookAndFeel on the form all controls (old and newly added, even on a newlu created form) still get/have the caramel skin again and not the choosen standard.
<<
This behavior is by design, controls are not receiving any notification about the fact that the DefaultLookAndFeel has been destroyed and as a result they are not repainted immediately. Controls will be only refreshed after reopening the application.

Thanks,
Stan.