Xtreme Toolkit Pro

Xtreme Toolkit Pro is the most comprehensive interface control package in MFC development. It provides 11 mainstream Visual C++ MFC controls for Windows development. Including Command Bars, Controls, Chart Pro, Calendar, Docking Pane, Property Grid, Report Control, Shortcut Bar, Syntax Edit, and Skin Framework and Task Panel.

I. Installation instructions

1) The installation package in the xtremetoolkitPro folder is installed

2) Find C: Program Files Codejock Software MFC Xtreme ToolkitPro v15.3.1 Workspace ToolkitPro Set Debug compilation mode (Unicode Deubg when first opened) to fully compile

3) At this time, the compiler will report an error, find the error location, paste the following section of code in the past, re-compile

COLORREF TopColorOut, TopColorIn, BottonColorOut, BottonColorIn;

case splitBorder:

if (pSplitter->IsBorderVisible())
{
TopColorOut = m_crOuterBorder.clrDark;
BottonColorOut = m_crOuterBorder.clrLight;
TopColorIn = m_crInnerBorder.clrDark;
BottonColorIn = m_crInnerBorder.clrLight;
}
else
{
TopColorOut = m_crBack;
BottonColorOut = m_crBack;
TopColorIn = m_crBack;
BottonColorIn = m_crBack;
}
pDC->Draw3dRect(rect, TopColorOut, BottonColorOut);
rect.InflateRect(-CX_BORDER, -CY_BORDER);
pDC->Draw3dRect(rect, TopColorIn, BottonColorIn);
return;
Copy the code

4) The Debug file can be successfully compiled. After the Debug file is successfully compiled:

C: Program Files Codejock Software MFC Xtreme ToolkitPro v15.3.1 Bin vc60 toolKitPro1531vc60d. DLL Toolkitpro1531vc60. DLL);

C: Program Files Codejock Software MFC Xtreme ToolkitPro v15.3.1 Lib vc60 toolKitPro1531vc60d. Lib Toolkitpro1531vc60. lib);

C) one DLL file, one lib file; DLL files in C:\Windows\System32 directory; C:\Program Files\Microsoft Visual Studio\VC98\MFC\ lib; Note: When migrating software, copy DLL and lib directly to the code project directory to be used.

5) At this point, the Codejock skin can be used normally through the software code

Ii. Operation Steps of new project (overall modification of interface style)

1) Copy the XTPFile directory to the root directory of the current project

2) Add “XTPFile” – “XTPSource” path to “Tools” – “options” – “directory” – “Include File” in VC development environment;

3)Stdafx.h add code:

#include <XTToolkitPro.h> // Codejock Software Components

4) Add the following code to App::InitInstance() :

CXTPWinDwmWrapper().SetProcessDPIAware();
AfxOleInit();
TCHAR szStylesPath[_MAX_PATH];
VERIFY(::GetModuleFileName(AfxGetApp()->m_hInstance, szStylesPath, _MAX_PATH));
CString m_strStylesPath;
m_strStylesPath = szStylesPath;
int nIndex = m_strStylesPath.ReverseFind(_T('\\'));
if (nIndex > 0)
{
m_strStylesPath = m_strStylesPath.Left(nIndex);
}
else
{
m_strStylesPath.Empty();
}
CString str = "";
str = m_strStylesPath.Right(5);
if ( "Debug" == str )
{
m_strStylesPath = m_strStylesPath.Left(nIndex-6);
m_strStylesPath += _T("\\XTPFile \\XTPStyles \\");
}
else if ( "lease" == str )
{
m_strStylesPath = m_strStylesPath.Left(nIndex-8);
m_strStylesPath += _T("\\XTPFile \\XTPStyles \\");
}
else
{
m_strStylesPath += _T("\\XTPFile \\XTPStyles\\");
}
XTPSkinManager()->SetApplyOptions(XTPSkinManager()->GetApplyOptions() | xtpSkinApplyMetrics);
XTPSkinManager()->LoadSkin(m_strStylesPath+_T("Vista.cjstyles"),_T("NormalBlack2.ini"));
Copy the code

/* All skin parameters are set as follows: WinXP.Luna.cjstyles NormalBlue.ini / NormalAqua.ini WinXP.Royale.cjstyles NormalRoyale.ini Office2007.cjstyles NormalBlue.ini/NormalAqua.ini/NormalSilver.ini/NormalBlack.ini Vista.cjstyles NormalBlue.ini/NormalSilver.ini/NormalBlack.ini/NormalBlack2.ini Codejock.cjstyles NormalBlue.ini/NormalBlack.ini Office2010. Cjstyles NormalBlue. Ini/NormalSilver. Ini/NormalBlack ini # endif three. Engineering software porting with Codejock interface library

When a development project needs to be ported to a target host, there is no need to install Codejick, just do the following:

Place the XTPFile folder and executable files in the same directory; Add “XTPFile” – “XTPSource” path to VC development environment “tools” – “options” – “directory” – “Include File”; Place the following four files in the XTPFile folder in the same directory as the executable; ToolkitPro1531vc60D. DLL, ToolkitPro1531vc60. DLL

ToolkitPro1531vc60D lib, ToolkitPro1531vc60. Lib

4. Possible problems with Codejock usage

The CodeJock skin runs in Debug mode on XP and needs to replace mfCD42d. DLL and mfCO42D. DLL in the System32 folder. If the operation still reports “memory access error”, continue to replace the DLL that reported the error. XP Release mode, WIN7 Debug and Release mode can be used normally. — — — — — — — — note: this article to CSDN blogger “GuitarCoder” of the original article The original link: blog.csdn.net/GuitarCoder…