MFC高级编程：控件定制与对话框设计

需积分: 34 182 浏览量更新于2024-07-21 收藏 1.81MB PDF 举报

MFC高级编程是一门深入讲解Microsoft Foundation Classes (MFC)的课程，它着重于实现高级界面设计和控件操作。本文档涵盖了多个关键主题，旨在帮助开发者提升在Windows应用程序中的用户体验。首先，章节1主要探讨了工具栏和对话框栏的高级使用。1.1节讲述了如何添加额外的 docking 工具栏，包括创建默认工具栏、工具栏的具体实现以及消息映射。开发者需要学习如何新增工具栏资源，并声明新的成员变量来支持定制功能。这部分介绍了如何通过`CommandMessageMapping`来处理命令消息。 1.2节介绍了模仿单选按钮和复选框的行为，这对于实现用户交互式控件非常重要。通过实例展示了如何使用`RadioButton`和`CheckBox`控件，以及如何使用布尔类型变量来控制它们的状态。接下来，1.3节详细解释了`CheckBox`的实现，特别是`FunctionCButton::SetButtonInfo`函数的使用，它允许程序员设置按钮的信息，进一步定制控件外观。 1.4节探讨了连续命令ID的消息映射，这对于管理一组相关的命令很有用，可以修改ID并保持逻辑连贯性。这部分内容强调了工具栏尺寸固定和组合框的添加。 1.5到1.8节涉及工具栏的更多细节，如调整大小、修改默认样式，以及对话框栏的使用，包括可调整大小的对话框和自定义对话框类。这些部分展示了如何动态布局控件以及如何利用新类进行操作。 2.1节转向菜单的设计，介绍了如何处理`WM_COMMAND`和`UPDATE_COMMAND_UI`消息，以及如何响应命令、启用或禁用菜单项、更改菜单文本，甚至检查菜单项是否被选中。这部分是菜单操作的核心内容。 2.2节深入研究右键弹出菜单（PopUp Menu），开发者将学习如何添加菜单资源、捕获右键点击事件，从而增强用户的交互体验。总结起来，MFC高级编程涵盖了一系列实用的主题，从基础控件定制到高级交互设计，有助于开发者创建更专业、功能丰富的Windows应用程序。通过掌握这些技术，开发者能够构建出更具吸引力和易用性的用户界面。

xvi

Program Manager

Summary

CONTEXT SENSITIVE HELP

16.1 Context Sensitive Help for Menu Commands

Context Sensitive Help

Context Sensitive Help for Menu Commands

Sample

New Commands

Editing “AfxCore.rtf”

ID Mapping

Help Topics Dialog Box

16.2 Context Sensitive Help for Common Controls

Supporting Context Sensitive Help in Dialog Box

ID Naming Rules

Enabling Context Sensitive Help for Common Controls

Function CWnd::OnHelpInfo(…)

Displaying Help in a Pop up Window

Summary

INDEX

Chapter 1. Tool Bar and Dialog Bar

Chapter 1

Tool Bar and Dialog Bar

ool bar and dialog bar are used extensively in all types of applications. They provide users with a

better way of executing application commands. Generally a tool bar comprises a series of buttons;

each button represents a specific command. A command implemented by the tool bar can be linked

directly to a menu command, in which case the two items share a same command ID. Both menu

and tool bar handle WM_COMMAND message for executing commands. Besides, they also handle

UPDATE_COMMAND_UI message to set the state of a button or a menu item. In fact, this message is very

effective in enabling, disabling, and setting checked or unchecked state for a command.

While tool bar usually contains bitmap buttons, dialog bar can include many other type of controls that

can be used in a dialog box, such as edit control, spin control, etc. Both tool bar and dialog bar can be

implemented either as floated or docked, this gives users more choices in customizing the user interface of

an application.

In MFC, classes that can be used to implement the tool bar and dialog bar are CToolBar and

CDialogBar respectively. Both of them are derived from class CControlBar, which implements bar

creation, command message mapping, control bar docking and floating (both tool bar and dialog bar are

called control bar). Besides the default attributes, class CToolBar further supports bitmap button creation,

automatic size adjustment for different states (docked or floated). A dialog bar can be treated as a dialog

box (There is one difference here: a dialog bar can be either docked or floated, a dialog box does not have

this feature): its implementation is based on a dialog template; all the common controls supported by dialog

box can also be used in a dialog bar; their message mapping implementations are exactly the same.

A standard SDI or MDI application created by Application Wizard will have a default dockable tool

bar. From now on we will discuss how to add extra tool bars and dialog bars, how to implement message

mapping for the controls contained in a control bar, and how to customize their default behavior.

1.1. Adding an Extra Docking Tool Bar

Default Tool Bar

When using Application Wizard to generate SDI or MDI application skeleton, we can ask it to create a

default docking tool bar for us. This can be done in the step 4 (see Figure 1-1). The default tool bar shares

the same ID with the mainframe menu. It has eight bitmap buttons, which are all shortcuts to the menu

commands. After executing this application, we will see a tool bar docked to the top border of the

mainframe window. By using the mouse, we can easily either float it or dock it to other borders.

The tool bar resource can be opened in the Developer Studio. If we click “ResourceView” tab at the

bottom of “Workspace” window, all the resources being used by the application will be listed within the

window. If we asked Application Wizard to add a default tool bar for us, we will see a “Toolbar” resource

node. By expanding this node (clicking on “+” node button or double clicking on the label), we will see all

tool bar resources used by the application. If we double click on “IDR_MAINFRAME” ID, the tool bar bitmap

will be displayed in “Tool Bar Edit” window. We can edit or delete an existing bitmap (each bitmap will be

used to create a bitmap button). We can also add new bitmaps and assign them command IDs. When doing

this, we can either use an existing menu command ID or a newly created one. In the latter case, we need to

implement message mapping afterwards.

Chapter 1. Tool Bar and Dialog Bar

The Application Wizard does an excellent job in adding a very powerful tool bar. Nevertheless, as a

programmer, we are kept from knowing what makes all these happen. If we need to make changes to the

default tool bar (for example, we want it to be docked to the bottom border instead of top border at the

beginning), which part of the source code should we modify? Obviously, we need to understand the

essentials of tool bar implementation in order to customize it.

Like menu, generally tool bar is implemented in the mainframe window. When creating a mainframe

menu, we need to prepare a menu resource, use class CMenu to declare a variable, then use it to load the

menu resource. Creating a tool bar takes similar steps: we need to prepare a tool bar resource, use class

CToolBar to declare a variable, which can be used to load the tool bar resource. After the tool bar resource

is loaded successfully, we can call a series of member functions of CToolBar to create the tool bar and

customize its styles.

After creating a standard SDI or MDI application using Application Wizard (with “Docking toolbar”

check box checked in step 4, see Figure 1-1), we will find that a CToolBar type variable is declared in class

CMainFrame:

Figure 1-1: Let Application Wizard add a default dockable tool bar

Check here to let

Application Wizard

add a default

dockable tool bar

for us

class CMainFrame : public CFrameWnd

{

……

protected: // control bar embedded members

CStatusBar m_wndStatusBar;

CToolBar m_wndToolBar;

……

}

The newly declared variable is m_wndToolBar. By tracing this variable, we will find out how the tool

bar is implemented.

Tool Bar Implementation

Tool bar creation occurs in function CMainFrame::OnCreate(…), where the mainframe window is

being created. Tool bar is created after function CFrameWnd::OnCreate(…) is called, which creates the

default mainframe window. Creating a tool bar takes following steps:

1) Call CToolBar::Create(…) to create tool bar window.

1) Call CToolBar::LoadToolBar(…) to load the tool bar resource. We need to pass a tool bar resource ID

to this function.

Chapter 1. Tool Bar and Dialog Bar

1) Call CToolBar::SetBarStyle(…) to set the attributes of the tool bar. For example, by setting different

flags, we can let the tool bar have fixed or dynamic size. Besides this, we can also enable tool tips and

flybys for tool bar buttons.

1) To make the tool bar dockable, we need to call function CToolBar::EnableDocking(…) and pass

appropriate flags to it indicating which borders the tool bar could be docked (We can make the tool bar

dockable to all four borders, or only top border, bottom border, etc.)

1) To dock the tool bar, we need to call function CMainFrame::DockControlBar(…). If we have more than

one tool bar or dialog bar, this function should be called for each of them.

We need above five steps to implement a tool bar and set its attributes.

Message Mapping

Since tool bars are used to provide an alternate way of executing commands, we need to implement

message mapping for the controls contained in a tool bar. This will allow the message handlers to be called

automatically as the user clicks a tool bar button. The procedure of implementing message mapping for a

tool bar control is exactly the same with that of a menu item. In MFC, this is done through declaring an

afx_msg type member function and adding macros such as ON_COMMAND and ON_UPDATE_COMMAND_UI.

The message mapping could be implemented in any of the four default classes derived from CWinApp,

CFrameWnd, CView and CDocument. Throughout this book, we will implement most of the message

mappings in document. This is because for document/view structure, document is the center of the

application and should be used to store data. By executing commands within the document, we don’t bother

to obtain data from other classes from time to time.

The following lists necessary steps of implementing message mapping:

1) Declare afx_msg type member functions.

1) Implement these member functions for message handling.

1) Add message mapping macros between BEGIN_MESSAGE_MAP and END_MESSAGE_MAP (which are

generated by Application Wizard). We need to use ON_COMMAND macro to map WM_COMMAND message,

and use ON_UPDATE_COMMAND_UI macro to implement user interface updating. The message mapping

should have the following format:

BEGIN_MESSAGE_MAP(class name, base class name)

//{{AFX_MSG_MAP(class name)

ON_COMMAND(command ID, member function name)

ON_UPDATE_COMMAND_UI(command ID, member function name)

//}}AFX_MSG_MAP

END_MESSAGE_MAP()

Most of the time message mapping could be implemented through using Class Wizard. In this case we

only need to select a command ID and confirm the name of message handler. Although Class Wizard does

an excellent job in implementing message mapping, sometimes we still need to add it manually because

Class Wizard is not powerful enough to handle all cases.

Adding New Tool Bar Resource

Now that we understand how the default tool bar is implemented, it is easy for us to add extra tool

bars. We can declare CToolBar type variables in class CMainFrame, create tool bars and set their styles in

function CMainFrame::OnCreate(…). Then we can map tool bar command IDs to member functions so that

the commands can be executed by mouse clicking.

Sample 1.1-1\Bar and 1.1-2\Bar demonstrate the above procedure. In the two applications, apart from

the default tool bar, an extra tool bar that has four different buttons is added. Each button is painted with a

different color: red, green, blue and yellow. If we click on one of them, a message box will pop up telling

us the color of the button.

First we need to use Application Wizard to create a standard SDI application named “Bar”, leaving all

the settings as default. This will generate an application with a mainframe menu, a dockable tool bar and a

status bar. The default four class names are CBarApp, CMainFrame, CBarDoc, CBarView.

Chapter 1. Tool Bar and Dialog Bar

Before modifying source code to add the second tool bar, we need to prepare the tool bar resource. In

order to do this, we need the following steps to create a tool bar resource that contains four bitmap buttons:

1) Load the application project into Developer Studio.

1) Execute Insert | Resource… command from the menu (or press CTRL+R keys). We will be prompted

to select resource type from a dialog box. If we highlight “toolbar” node and click the button labeled

“New”, a new blank tool bar resource “IDR_TOOLBAR1” will be added to the project. Since default ID

doesn’t provide us much implication, usually we need to modify it so that it can be easily understood.

In the samples, the newly added tool bar resource ID is changed to IDR_COLOR_BUTTON. This can be

implemented by right clicking on “IDR_TOOLBAR1” node in WorkSpace window, and selecting

“Properties” item from the popped up menu. Now a property sheet whose caption is “Toolbar

properties” will pop up, which contains an edit box that allows us to modify the resource ID of the tool

bar.

1) Using the edit tools supplied by the Developer Studio, add four buttons to the tool bar, paint bitmaps

with red, green, blue and yellow colors, change their IDs to ID_BUTTON_RED, ID_BUTTON_GREEN,

ID_BUTTON_BLUE, ID_BUTTON_YELLOW. The tool bar bitmap window could be activated by double

clicking on the tool bar IDs contained in the WorkSpace window, the graphic tools and color can be

picked from “Graphics” and “Colors” windows. If they are not available, we can enable them by

customizing the Developer Studio environment by executing Tools | Customize… command from the

menu.

Declaring New Member Variable

After the resource is ready, we can add code to implement the tool bar.

The first step is to declare a new variable using CToolBar in class CMainFrame:

class CMainFrame : public CFrameWnd

{

……

protected:

CStatusBar m_wndStatusBar;

CToolBar m_wndToolBar;

CToolBar m_wndColorButton;

……

};

The new variable is m_wndColorButton, it is added right after other two variables that are used to

implement the default tool bar and status bar.

Next, we can open file “MainFrm.cpp” and go to function CMainFrame::OnCreateClient(…). In

Developer Studio, the easiest way to locate a member function is to right click on the function name in

“WorkSpace” window, then select “Go to Definition” menu item from the popped up menu. Let’s see how

the default tool bar is created:

……

if (!m_wndToolBar.Create(this) ||

!m_wndToolBar.LoadToolBar(IDR_MAINFRAME))

{

TRACE0("Failed to create toolbar\n");

return -1;

}

……

Function CToolBar::Create(…) is called first to create the tool bar window. Then

CToolBar::LoadToolBar(…) is called to load the bitmaps (contained in tool bar resource IDR_MAINFRAME).

When calling function CToolBar::Create(…), we need to specify the parent window of the tool bar by

providing a CWnd type pointer (Generally, a tool bar must be owned by another window). Because this

function is called within the member function of class CMainFrame, we can use “this” as the pointer of

parent window.

The following code fragment shows how the styles of the default tool bar are set:

剩余529页未读，继续阅读

zloveh123

粉丝: 1
资源: 3

MFC高级编程：控件定制与对话框设计

基于幼儿发展的绘本在小班幼儿教育中的实践与优化策略

智慧林业整体解决方案PPT(27页).pptx

城市小学生课间活动现状及改进措施分析

超星nm10 aarch64平台ubuntu使用移远EC200-CN4G/5G卡

两级式单相光伏并网仿真（注意版本matlab 2021a） 前级采用DC-DC变电路，通过MPPT控制DC-DC电路的pwm波来实现最大功率跟踪,mppt采用扰动观察法，后级采用桥式逆变，用spwm波

电力电子技术中最大电流自动均流法的小信号建模及其控制环路分析

中国大学生服务外包创新创业大赛A类企业命题详解及技术要求

Java源码ssm框架疫情居家办公OA系统演示录像-毕业设计论文-期末大作业.rar

优化铷原子四波混频实现微波-光学转换的研究

大学数学实验期末大作业指南：探究性与实践性实验要求详解

最新资源

两级式单相光伏并网仿真（注意版本matlab 2021a）前级采用DC-DC变电路，通过MPPT控制DC-DC电路的pwm波来实现最大功率跟踪,mppt采用扰动观察法，后级采用桥式逆变，用spwm波