thanks for the answer. You ar partially right.

If i use ApplyWindow for the form containing the ActiveX, than the dialog above is now correct skinned.

 

I can do then skinning for open- and preview-dialogs and it works fine.

 

Only the Designer has some problems.

If i open some dialogs, the background will be erased and than show the controls, after that the form is skinned again:

 

 

If i than click the tabs for and back, it's drawn but not in the wanted layout.

 

I think i can supress the skinning for the designer, because the other dialogs are skinned correct.

If you have a solution in future, let me know.

 

PS:

I work now with List and Label 14 !!!

 

Yes see same with this List and Label ActiveX :-(

 

I traced it and they catch WM_ERASEBGND in own code and manually fill backgroudn and don't give change SkinFramework use skinned color.  Not sure what code they have to fill background :(

The windows are build from external dll's:

 

 

The unskinned part is a class named "cmbtDialog1432W" and is embed in "#32770"-class.

How can i tell the skinframework to skin this Dialog ?

I don't know a correct BaseClassName, because the foreign class is like a default dialogframe #32770, but this is sometimes embedded in an other frame (like docked).

Also the background-skinning does not work.

Because i don'r know a windows-handle, i can't use EnableThemeDialogTexture.

 

An other class is the mainwindow and it should be skinned as mainwindow. I can only select a MDIClient as baseclass, but this don't work, windows-caption disapears.

 

Any idea to solve this ?