VCL -- Understanding the Message-Handling System
Understanding the Message-Handling System
http://docwiki.embarcadero.com/RADStudio/XE7/en/Understanding_the_Message-Handling_System
All VCL classes have a built-in mechanism for handling messages, called message-handling methods or message handlers.
The basic idea of message handlers is that the class receives messages of some sort and dispatches them,
calling one of a set of specified methods depending on the message received.
If no specific method exists for a particular message, there is a default handler.
The following diagram shows the message-dispatch system:
Dispatching Messages
http://docwiki.embarcadero.com/RADStudio/XE7/en/Dispatching_Messages
When an application creates a window, it registers a window procedure with the Windows kernel.
The window procedure is the routine that handles messages for the window.
Traditionally, the window procedure contains a huge case statement with entries for each message the window has to handle.
Keep in mind that "window" in this sense means just about anything on the screen:
each window, each control, and so on.
Every time you create a new type of window,
you have to create a complete window procedure.
The VCL simplifies message dispatching in several ways:
- Each component inherits a complete message-dispatching system.
- The dispatch system has default handling.
You define handlers only for messages you need to respond to specially. - You can modify small parts of the message handling and rely on inherited methods for most processing.
The greatest benefit of this message dispatch system is that you can safely send any message to any component at any time.
If the component does not have a handler defined for the message, the default handling takes care of it, usually by ignoring the message.
Tracing the flow of messages
The VCL registers a method called MainWndProc as the window procedure for each type of component in an application.
MainWndProc contains an exception-handling block, passing the message structure from Windows to a virtual method called WndProc
and handling any exceptions by calling the application class's HandleException method.
MainWndProc is a nonvirtual method that contains no special handling for any particular messages.
Customizations take place in WndProc, since each component type can override the method to suit its particular needs.
WndProc methods check for any special conditions that affect their processing so they can "trap" unwanted messages.
For example, while being dragged, components ignore keyboard events,
so the WndProc method of TWinControl passes along keyboard events only if the component is not being dragged.
Ultimately, WndProc calls Dispatch, a nonvirtual method inherited from TObject,
which determines which method to call to handle the message.
Dispatch uses the Msg field of the message structure to determine how to dispatch a particular message.
If the component defines a handler for that particular message, Dispatch calls the method.
If the component does not define a handler for that message, Dispatch calls DefaultHandler.
The WndProc Method
http://docwiki.embarcadero.com/RADStudio/XE7/en/The_WndProc_Method
WndProc is the default Windows message handling function for a given control,
and the first method that receives messages on a form.
The WndProc method can be overridden in order to implement specific message responses.
WndProc passes any unhandled messages to the Dispatch method.
VCL controls have a property called WindowProc that points to the WndProc method.
This property can be used to replace or subclass the window procedure.
Before assigning a new value to WindowProc, the original value should be stored.
After completing any specialized message handling, call the original WindowProc
to make sure the normal message processing works as expected.
Note: If you are a component writer customizing the window procedure for a descendent class, y
ou should override theWndProc method instead of replacing or subclassing it.
Note: When overriding WndProc to provide specialized responses to messages,
be sure to call the inherited WndProc method at the end,
in order to dispatch any unhandled messages.
Trapping Messages
http://docwiki.embarcadero.com/RADStudio/XE7/en/Trapping_Messages
Under some circumstances, you might want your components to ignore messages.
That is, you want to keep the component from dispatching the message to its handler.
To trap a message, you override the virtual method WndProc.
For VCL components, the WndProc method screens messages
before passing them to the Dispatch method,
which in turn determines which method gets to handle the message.
By overriding WndProc, your component gets a chance to filter out messages before dispatching them.
An override of WndProc for a control derived from TWinControl looks like this:
procedure TMyControl.WndProc(var Message: TMessage);
begin
{ tests to determine whether to continue processing } inherited WndProc(Message);
end;
The TControl component defines entire ranges of mouse messages that it filters when a user is dragging and dropping controls.
Overriding WndProc helps this in two ways:
- It can filter ranges of messages instead of having to specify handlers for each one.
- It can preclude dispatching the message at all, so the handlers are never called.
VCL -- Understanding the Message-Handling System的更多相关文章
- Android Message Handling Mechanism
转自:http://solarex.github.io/blog/2015/09/22/android-message-handling-mechanism/ Android is a message ...
- Understanding the WPF Layout System
Many people don't understand how the WPF layout system works, or how that knowledge can help them in ...
- Android Message handling (based on KK4.4)
一.几个关键概念 1.MessageQueue:是一种数据结构,见名知义,就是一个消息队列.存放消息的地方.每个线程最多仅仅能够拥有一个MessageQueue数据结构. 创建一个线程的时候,并不会自 ...
- 7.4 GRASP原则四:控制器 Controller
4.GRASP原则四:控制器 Controller What first object beyond the UI layer receives and co-ordinates (control ...
- Meandering Through the Maze of MFC Message and Command Routing MFC消息路由机制分析
Meandering Through the Maze of MFC Message and Command Routing Paul DiLascia Paul DiLascia is a free ...
- TAxThread - Inter thread message based communication - Delphi
http://www.cybletter.com/index.php?id=3 http://www.cybletter.com/index.php?id=30 Source Code http:// ...
- System IPC 与Posix IPC(semaphore信号灯)
POSIX下IPC主要包括三种: posix message queue posix semaphores posix shared memory sysytem v IPC包括: system v ...
- Exception Handling Considered Harmful
异常处理被认为存在缺陷 Do, or do not. There is no try. - Yoda, The Empire Strikes Back (George Lucas) by Jason ...
- System中记录体函数命名怪异
//1019unit System; 中发现记录体函数命名怪异//乍一看,很怪异,其实是结构体里面 的变量后面直接写 函数类型了.不像传统先定义T***Event = procedure(S ...
随机推荐
- BroadcastReceiver应用详解
今天我们来讲一下Android中BroadcastReceiver的相关知识. BroadcastReceiver也就是“广播接收者”的意思,顾名思义,它就是用来接收来自系统和应用中的广播. 在And ...
- .net core学习
http://www.cnblogs.com/artech/ http://www.blogs8.cn/posts/AA0E630 http://pan.baidu.com/s/1bo4fJ47 ht ...
- hdu5248 序列变换
百度之星的题.其实最简单的方法是二分答案,我竟然没想到,直接去想O(n)的去了,最后导致滚粗... 题意就是给一个数列,要求把它处理成递增序列. 首先我想到了O(n^2)的算法,然后再优化成O(n)过 ...
- Cocos2d-android (01) 创建一个简单的cocos2d应用程序
下载Cocos2d-android的源代码:cocos2d-android-1 git@github.com:ZhouWeikuan/cocos2d.git 将项目导入到eclipse中.运行实例: ...
- Real Boxing 2
http://itunes.apple.com/ca/app/real-boxing-2/id932779605?mt=8&ign-mpt=uo%3D4
- Intellij IDEA开发第一个Android应用
1.创建一个项目 File——>New Project——>.......——>Finish 2.创建模块 3.MyActivity.java package com.example ...
- 分享一些前端chm文档
分享地址:http://yun.baidu.com/share/link?shareid=39230983&uk=1008683945 对于网络不好的人来说,离线文档更加方便.打开速度更快. ...
- Archlinux 踩坑实录
Archlinux 没声音 1. 排查驱动,声卡驱动没问题 2.排查alsa,alsa没问题(并确认声卡存在且取消静音) 3.抱着尝试的心态,安下VLC.然后提示找不到默认声卡设备(大概这个意思),通 ...
- 神奇的linux发行版 tiny core linux
首先官网在此 http://tinycorelinux.net/ 真正轻量级 名字里带有“tiny”又带有“core”,想必又是一个所谓的“轻量级”发行版. 轻量级我们见多了,debian号称是轻量级 ...
- Windows Server 2003单网卡搭建VPN
Windows Server 2003单网卡搭建VPN 1.打开[控制面板] --> [管理工具] --> [路由和远程访问] 2.鼠标右击你要管理的电脑 在弹出式菜单中选中[配置并启 ...