But this method doesn't work for the new themes, all I get is a completely black command bar, this is the same for all other controls as well.

Setting VisualTheme to xtpThemeOffice2013 instead makes buttons appear on the command bar but in a standard looking colour and the status bar is still completely black.

See these previous posts for examples with no solution...

http://forum.codejock.com/forum_posts.asp?TID=21821" rel="nofollow - http://forum.codejock.com/forum_posts.asp?TID=21821

http://forum.codejock.com/forum_posts.asp?TID=21733" rel="nofollow - http://forum.codejock.com/forum_posts.asp?TID=21733

Thanks

Note that the newer 2013 themes are set up quite a bit differently from their predecessors, but again the samples demonstrate this pretty clearly.

EDIT: Setting to new VS themes just GPFs the application so there is definitely some incompatibility with these newer themes and Openedge.

Are you certain about that? I'm using the MFC version of XTP, and the Office 2013 themes are definitely not implemented the same way as previous ones. In other words, in the MFC version you cannot use "xtpThemeResource" with the Office 2013 themes - "xtpThemeOffice2013" must be used instead, etc.

Yes that is the only difference which is what I mentioned in OP but it still doesn't work for us unfortunately and any of the VS themes just crash the app so clearly it just doesn't like them.

Cheers

The following code loads the Office 2013 resource DLL sets the resource handle to the MS Word INI settings file:

XTPThemeDLL()->SetHandle(xtpIniOffice2013Word);

Here's and example for Command Bars that calls SetTheme and enables frame themes for the ribbon control. 

CXTPPaintManager::SetTheme(xtpThemeOffice2013);

CXTPRibbonBar* pRibbonBar = DYNAMIC_DOWNCAST(CXTPRibbonBar, GetCommandBars()->GetMenuBar());
if (pRibbonBar)
{
    pRibbonBar->EnableFrameTheme();
}
	
CXTPCommandBars* pCommandBars = GetCommandBars();
if (pCommandBars)
{	
    pCommandBars->GetPaintManager()->RefreshMetrics();
    pCommandBars->RedrawCommandBars();
}
	
SendMessage(WM_NCPAINT);
RedrawWindow(0, 0, RDW_ALLCHILDREN|RDW_INVALIDATE);

The ActiveX samples are still in the process of getting updated, right now the MFC samples demonstrate this.  We will be adding examples for ActiveX by Beta 2.

Can you please provide an update on the recent status of the problem, if it's still relevant for you? If yes, we first need to stick to Office2013 and try to find out why it works for you in the sample but doesn't work in your application. I'd like to suggest starting with isolation test as there can be leftovers of even older version of SuitePro installed on your computer. When components of different versions are installed on one computer it's OK and the apps will work as the same components have different class IDs between versions, but it's not OK for development as there is one and only one instance of type library installed per component and some development environments rely on this type library, so there can a conflict. So, better try to install 17.0 on a separate computer or virtual OS where you are sure no SuitePro has been previously installed and do the tests of the sample and your application. You can also try to cleanup your development environment manually but in this case before installing 17.0 make sure no SuitePro traces left, use Ole View (Controls and Type Libraries group) for verification, all SuitePro entities start with 'Xtreme' word.

Keep us updated please.

Thank you.

Regards,

  Alexander

To be honest this is the least of our problems at the moment as we can just ignore the new themes. I'd be happier if the following issues were fixed (or workarounds offered) instead...