If I try to enable skinning in my mainframe create logic, I sometimes get crashes I think due to creation of child threads/windows. If i disable either the threading or skinning, my problems go away. If I delay the skinning until well after the application and all its threads are fully running (ie, through a user button click) then skinning works fine.

 

QUESTION: Is there any way to know when the skinning has been fully applied? Any message sent to mainframe or anything I can poll?

 

Also have a similar question relating to the ribbon.

 

QUESTION: Is there a way to know when the ribbon is done being actually created (rendered) the first time?

 

I have a long startup process involving reading 100 files (for a module based application) and I would like to delay the loading of these files until the application looks nice with the ribbon. If I don't delay, I see the traditional GUI and then a few seconds later, see it revert to the ribbon.

 

If a put a PeekMessage/DispatchMessage loop right after my ribbon creation but before the file loads, it helps but is not perfect.

 

Thanks.

Ribbon Must be created after you add it, and frame enabled after you cal pRibbpn->EnableThemeFrame();

 

What version you have? In 10.4 we added support of multithreaded for SkinFramework.

 

The ribbon painting is not my main concern. It is working ok.

 

But I do have a problem with the skins.

 

When is it safe to enable the skins?

 

What if other threads were being created (and those threaded created windows) while the main thread was still in the process of skinning?

I recommend enable it in constructor of CMainframe.