精通MFC高级编程：工具栏与对话栏技巧

5星 · 超过95%的资源需积分: 34 39 浏览量更新于2024-07-26 收藏 1.81MB PDF 举报

"Advanced MFC Programming"是一份详尽的Microsoft Foundation Classes (MFC)学习资料，专为深入理解MFC框架设计。这份文档涵盖了MFC高级编程的核心概念和技术，主要集中在工具栏和对话框栏的实现上。 1. **工具栏与对话栏**： - **添加额外的 docking 工具栏**: 学习如何在MFC应用中添加自定义工具栏，并探讨如何将其与窗口的布局管理集成。 - **默认工具栏与实现**: 深入剖析MFC中的DefaultToolBar及其内部工作原理，包括消息映射和资源管理。 - **命令消息映射**: 探讨如何为不同的命令ID设置响应函数，实现更精确的用户交互控制。 2. **模拟单选按钮和复选框行为**： - **RadioButton & CheckBox**：通过示例演示如何在工具栏中使用这些控件，以及如何使用布尔类型变量管理和设置它们的状态。 3. **工具栏功能扩展**： - **修改ID范围**：讲解如何处理连续的命令ID，以及如何根据需要进行调整。 - **固定工具栏大小**：介绍如何确保工具栏在不同屏幕尺寸下的正确显示。 - **添加组合框到工具栏**：展示如何集成更多复杂的选择功能。 4. **对话栏和可调整大小的对话框**： - **对话栏设计**：创建自定义对话栏类并实现动态布局。 - **可调整大小的对话框**：探讨如何让对话框内的控件适应用户界面的变化。 5. **额外交互元素**： - **飞入提示与工具提示**：实现鼠标悬停时的额外信息显示。 - **控制栏的切换**：讨论如何控制工具栏和对话栏的可见性，以优化用户体验。 6. **菜单系统**： - **处理WM_COMMAND和UPDATE_COMMAND_UI消息**：解释这两个消息在菜单操作中的作用。 - **右键快捷菜单**：介绍如何创建和管理弹出菜单，以及如何捕捉右键点击事件。这份文档提供了一个丰富的实践平台，适合MFC开发者进一步提升他们的技能，无论是对基础控件的深层次理解和应用，还是高级定制化的需求，都能从中获益匪浅。通过阅读和实践，读者将能够更好地构建功能完备且用户友好的应用程序。

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页未读，继续阅读

Shawna

粉丝: 0
资源: 2

精通MFC高级编程：工具栏与对话栏技巧

MFC界面设计高级教程

Advanced MFC

MFC.custom.advanced.programming.browser.rar_MFC Browser_browser_

Advanced 3D Game Programming with DirectX 8.0

MFC经典教程

MFC+Windows程序设计

Professional MFC with VC6

ActiveX programming with visual c++

Professional.MFC.with.VC6

.NET Programming with Visual C++: Tutorial, Reference, and Immediate Solutions

最新资源