This is a part of the Microsoft Foundation Classes C++ library.
Copyright (C) 1994-1995 Microsoft Corporation
All rights reserved.
This source code is only intended as a supplement to the
Microsoft Foundation Classes Reference and related
electronic documentation provided with the library.
See these sources for detailed information regarding the
Microsoft Foundation Classes product.
-------------------------------------------------------
MTMDI Sample Microsoft Foundation Classes Application
-------------------------------------------------------
The MTMDI sample illustrates an MFC user-interface thread, where user
interface events are processed in a thread separate from the main
application thread. This sample is a modified version of the single
thread MDI sample.
The MTMDI sample does not claim a strong rationale for putting the
bouncing ball window in a separate thread. An end-user would not be
able to detect the difference between the MDI and MTMDI samples on a
single processor machine. Even on a multi-processor machine, the
end-user would not be able to detect the difference given that the
ball movement is based on a window timer.
Further, the MTMDI sample does not claim a strong rationale for using
an MFC worker thread instead of an MFC user-interface thread. MFC worker
threads generally are easier to use and more appropriate than user-interface
threads for tasks that do not involve processing of user interface events.
The drawing of the bouncing ball could have been implemented in
a worker thread instead of a user-interface thread, if some technique
other than window timers were used to advance the ball. The use of the
window timer in a separate thread requires a message pump; therefore
the separate thread must be a user-interface thread instead of a worker
thread. To add slightly more justification for using a user-interface
thread, the MTMDI sample includes one additional user-interface feature
not in the MDI sample: you can click anywhere in the bounce window to
immediately change the position of the moving ball.
Although the MDI sample does not claim a strong rationale for using
threads, it nevertheless does illustrate techniques for implementing an
MFC user-interface thread. The remainder of this readme describes
the differences between the implementation of the single thread MDI
application and the multiple thread MTMDI application. These differences
illustrate that it is more difficult to implement an application with
a user-interface thread than a corresponding application that executes
in a single thread. This should be a warning that you should not use
user-interface threads unless you have good reasons.
The overall differences between the implementation of the MDI and MTMDI
samples are these:
1. The CBounceWnd window runs in a separate user-interface thread
in the MTMDI application.
2. In the MDI sample, CBounceWnd is derived from CMDIChildWnd. In the
MTMDI sample, CBounceWnd is derived from CWnd, and a CBounceWnd
window is a child of the MDI child window. In the MTMDI sample,
the CBounceWnd child window fills exactly the client area of the
parent MDI child window (a CMDIChildBounceWnd).
3. In the MDI sample, normal MFC command routing and command user-
interface initialization are used for menu commands associated with
the bounce window. In the MTMDI sample, the MDI child window's
OnCmdMsg function is overridden in order to send the OnCmdMsg
parameters via SendMessage to the CBounceWnd executing in the
separate thread. In general, SendMessage typically needs to be
used us to make calls from a window in one thread to a window in
another thread in an MFC application.
Note: The Hello window is left in the main application thread.
Implementing the Bounce window in a separate thread is sufficient
to illustrate the MFC multithread techniques.
This MTMDI sample does not directly illustrate a view running in a separate
thread, because MTMDI and the original MDI sample do not use MFC's
document/view architecture. Still, the design of MTMDI can be applied
to an application where you might want the view to run in a separate thread.
In general, you cannot successfully implement member functions of a CView
to run in a separate thread, because the MFC document/view architecture
relies on thread local storage (TLC) for some of the data that coordinates
documents and views. However, you can apply the design of MTMDI by
implementing a child window of the CView window, and processing user-
interface events of this child window in a separate thread.
The design of MTMDI is summarized below. For additional details, see
source code comments.
=================
CWinThread object
=================
The thread object for the bouncing ball window is implemented in
a CWinThread-derived class, CBounceThread, in mtbounce.cpp.
Beginning the user-interface thread
-----------------------------------
The overridden CMDIChildBounceWnd::OnCreate begins the thread for
the bouncing ball. There are two ways to begin an MFC user-interface
thread: (1) call AfxBeginThread, passing the CRuntimeClass of the
CWinThread-derived class; or (2) implement two-stage construction of
the CWinThread-derived object by new'ing it and then calling
CWinThread::CreateThread. We use the second method because it offers
the easiest way to pass the HWND of the CMainFrame window to the
thread, which needs the parent HWND to create the child window.
We simply pass the HWND to the CBounceThread constructor.
An alternative method is:
- call AfxBeginThread with a CREATE_SUSPENDED parameter;
- pass the parent HWND via a new CBounceThread::SetParentWnd function;
or make the CBounceThread::m_hwndParent member variable public and
set it directly; and then
- call CWinThread::ResumeThread.
Thread instance initialization
------------------------------
CWinThread::InitInstance is the only member function that must be
overridden for a user-interface thread. The implementation of
CBounceThread::InitInstance is typical in that it creates (using
CWnd::Create) the window that processes messages in the separate thread.
Terminating the user-interface thread
-------------------------------------
The easiest way to terminate a user-interface thread is to rely on
automatic termination of the thread when the main window associated with
the thread is destroyed. The only thing you need to do to implement
such automatic thread termination is to set the CWinThread::m_pMainWnd
to the main window. This is illustrated in CBounceThread::InitInstance.
The default CWnd::OnNcDestroy handler checks whether the window being
destroyed is the thread's m_pMainWnd and, if so, terminates the thread,
provided it isn't the main application thread.
Unless you change the default TRUE value of CWinThread::m_bAutoDelete,
the framework will automatically delete the CWinThread object when the
thread terminates.
Avoiding memory leak detection of CWinThread object
---------------------------------------------------
When the application terminates, it destroys each window in the window
hierarchy, and then, in debug mode, checks for memory leaks.
It is possible that the application will falsely detect a memory leak of the
CWinThread object before the user-interface thread has had a chance to
automatically terminate. The reported memory leak is false because
eventually the CWinThread object will be automatically destroyed anyway.
Nevertheless, the dumping of memory leak information can be disconcerting.
To avoid this, we use a "bounce thread killed" event. The CBounceThread
delete operator sets the event. The main application waits for this event
before terminating. It is better to set the event in the delete operator
rather than in the CBounceThread destructor, because it is remotely possible
that the applicati
没有合适的资源?快使用搜索试试~ 我知道了~
bcb系统例子 bcb系统例子
共2682个文件
cpp:852个
h:573个
dfm:321个
5星 · 超过95%的资源 需积分: 8 28 下载量 2 浏览量
2009-05-26
23:31:35
上传
评论 1
收藏 4.09MB RAR 举报
温馨提示
bcb系统例子 bcb系统例子bcb系统例子 bcb系统例子 bcb系统例子
资源推荐
资源详情
资源评论
收起资源包目录
bcb系统例子 bcb系统例子 (2682个子文件)
search.avi 21KB
dillo.avi 16KB
filecopy.avi 9KB
default.bmk 6KB
all.bmp 541KB
androm.bmp 302KB
back.bmp 301KB
nmlogo.bmp 41KB
board.bmp 20KB
gameover.bmp 19KB
field.bmp 17KB
blue.bmp 12KB
red.bmp 12KB
gold.bmp 12KB
main1b.bmp 5KB
srvrbig.bmp 3KB
live.bmp 3KB
dead.bmp 3KB
down.bmp 3KB
up.bmp 3KB
fwd.bmp 3KB
mainfrmb.bmp 3KB
formatbg.bmp 2KB
main1.bmp 2KB
mainfrm.bmp 2KB
cpalette.bmp 2KB
bitmap1.bmp 1KB
wordp48.bmp 1KB
srvr.bmp 1KB
toolbar.bmp 1KB
standard.bmp 1KB
toolbar.bmp 1KB
toolbar.bmp 1KB
toolbar.bmp 1KB
toolbar.bmp 1KB
formatba.bmp 1KB
replayd.bmp 1014B
replayu.bmp 1014B
replayf.bmp 1014B
toolbar.bmp 958B
blue.bmp 898B
toolbar.bmp 838B
itoolbar.bmp 718B
tversioninfo.bmp 630B
toolbar.bmp 598B
toolbar.bmp 478B
toolbar.bmp 478B
tsingleappinstance.bmp 406B
bmtreeno.bmp 374B
bmp00002.bmp 374B
bitmap2.bmp 374B
bmtreedo.bmp 374B
bmtreebi.bmp 374B
bmp00003.bmp 374B
bmp00001.bmp 374B
bmtreefi.bmp 374B
bitmap1.bmp 374B
font.bmp 358B
cross.bmp 358B
fhoriz.bmp 358B
leftarr.bmp 358B
colors.bmp 358B
dcross.bmp 358B
fsolid.bmp 358B
brush.bmp 358B
fclear.bmp 358B
fvert.bmp 358B
fdiag.bmp 358B
bdiag.bmp 358B
rightarr.bmp 358B
ellipse.bmp 334B
run.bmp 246B
btnctl.bmp 238B
circ1ctl.bmp 238B
floppy.bmp 190B
fixed.bmp 190B
network.bmp 190B
rulerdom.bmp 182B
rulerupm.bmp 182B
rulerdo.bmp 182B
rulerup.bmp 182B
dashdot.bmp 178B
clear.bmp 178B
dashed.bmp 178B
dotted.bmp 178B
dashdot2.bmp 178B
rulerblm.bmp 166B
rulerbl.bmp 166B
rulerta.bmp 142B
rulertam.bmp 142B
wordpad.bpf 853B
cmnctrl2.bpf 539B
cmnctrl1.bpf 539B
collect.bpf 453B
superpad.bpf 395B
chkbook.bpf 340B
chatsrvr.bpf 309B
chatter.bpf 306B
mtrecalc.bpf 290B
oldbars.bpf 284B
共 2682 条
- 1
- 2
- 3
- 4
- 5
- 6
- 27
资源评论
- shuiren12302014-01-05例子不错啊。。。
- shen8910282012-02-13各种小例子,适合初学者啊
- 普通网友2013-05-27我是初学者,资源很好
- cll_spring12013-03-26感谢提供的资料
songguozhi
- 粉丝: 83
- 资源: 79
上传资源 快速赚钱
- 我的内容管理 展开
- 我的资源 快来上传第一个资源
- 我的收益 登录查看自己的收益
- 我的积分 登录查看自己的积分
- 我的C币 登录后查看C币余额
- 我的收藏
- 我的下载
- 下载帮助
安全验证
文档复制为VIP权益,开通VIP直接复制
信息提交成功