C / C++ / MFC

R.Bischoff | C++
 
.NET, Kommst du mit?

Manually Add the Context Hooks
If you already have a program and need to add help, you can manually edit the files to create the necessary
hooks.
To add context sensitive help manually:
1. Add the necessary message map entries in the message map of the Main Frame class. If you created the
program with the MFC App Wizard and specified that you wanted context help, these items should already
be in the file.
ON_COMMAND(ID_HELP_FINDER, CMDIFrameWnd::OnHelpFinder)
ON_COMMAND(ID_HELP, CMDIFrameWnd::OnHelp)
ON_COMMAND(ID_CONTEXT_HELP, CMDIFrameWnd::OnContextHelp)
ON_COMMAND(ID_DEFAULT_HELP, CMDIFrameWnd::OnHelpFinder)
2. Copy the What's This? Help icon into a button on your toolbar. This icon is available as a bitmap in
C:\Program Files\Microsoft Visual Studio\Common\Graphics\Bitmaps\OffCtlBr\Small\Color\help.bmp.
3. Assign ID_CONTEXT_HELP to the What's This? Help button.
Note:
• This creates the same basic hooks in the program as the App Wizard, but does not generate a framework
help file or the .hm file with the topic ID mapping. You will need to create a list of IDs for the help author
to use.
Override the Default Context Help Behavior
The default WinHelp call made from the hooks automatically created by the App Wizard opens each help topic
in the main WinHelp window. Unfortunately the current recommended behavior is:
• Control level help is opened in a popup.
• Window level help is opened in a secondary window.
To create these conditions, you must override the default functions.
To create currently recommended behavior:
1. In the Main Frame class, create an OnHelpInfo function using the Class Wizard:
BOOL CMainFrame::OnHelpInfo(HELPINFO* pHelpInfo)
{
return TRUE;
}
This effectively disables the function, and is necessary because, in combination with the next override, all
topics accessed through the F1 key will be called twice. Unfortunately you cannot use the OnHelpInfo
function in the Main Frame since (unlike in dialog boxes) it is triggered only by the F1 key and not by Shift-
F1 or the key.
2. In the Main Frame class, create a WinHelp function using the Class Wizard:
void CMainFrame::WinHelp(DWORD dwData, UINT nCmd)
{
CWinApp* theApp = AfxGetApp();
CString helpFilePath = theApp->m_pszHelpFilePath;
switch ( dwData ) {
case HIDR_MAINFRAME:
case HIDR_MFCWIZTYPE:
case HIDD_ABOUTBOX:
case HIDD_TESTDLG:
//Topics that need to go into a secondary window.
helpFilePath = helpFilePath + ">second";
::WinHelp(m_hWnd, helpFilePath, HELP_CONTEXT, dwData);
break;
case WHATEVER
//Topics that need to go into a different secondary window
...
break;
default:
//All the rest are popups
::WinHelp(m_hWnd, helpFilePath, HELP_CONTEXTPOPUP, dwData);
break; }
}
Tips:
• It is often easier to create a separate function or class to process the help calls and open topics in the
correct window. This can be part of the main program or can be created as a separate DLL. The main
advantage of a DLL is that it can be called from other programs if necessary.
• If you want the help author to be able to control the help file and window called by this function, class, or
DLL, put the help file and window definitions in an INI file (you can use the topic number as the key) and
look them up before calling Help. If you include the help type as an INI file entry you can easily call
multiple types of user assistance from the same program.

char szFileName[ _MAX_PATH ];
GetModuleFileName( AfxGetInstanceHandle(), szFileName, sizeof(szFileName) );
  
char szDrive[ _MAX_DRIVE ];
char szDir[ _MAX_DIR ];
_splitpath( szFileName, szDrive, szDir, NULL, NULL );
  
CString strTheFolderYouWant;
strTheFolderYouWant.Format( "%s%s", szDrive, szDir );

char szFileName[ _MAX_PATH ];
GetModuleFileName( GetModuleHandle(NULL), szFileName, sizeof(szFileName) );
  
char szDrive[ _MAX_DRIVE ];
char szDir[ _MAX_DIR ];
_splitpath( szFileName, szDrive, szDir, NULL, NULL );
  
char szTheFolderYouWant[ _MAX_PATH ];
sprintf( szTheFolderYouWant, "%s%s", szDrive, szDir );