blocks|key|2748617|text|DDX_Control()在引擎盖下执行SubclassWindow()。SubclassDlgItem是SubclassWindow(GetDlgITem())的快捷方式。通常(这里的泛指)使用SubclassWindow的人是在DDX_Control出现之前(1995年前？)养成这个习惯的人。而且从来没有真正进入过MFC模式，或者人们从左右的博客片段中复制和粘贴他们的程序。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2748618|因此，尽管使用SubclassDlgItem()在技术上不会有什么不同，但为了清晰起见，请使用DDX_Control()。|2748619|entityMap^0|0|D|K|G|11|F|1H|S|2Q|E|38|B|0|7|H|1B|D|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]|$9|O|A|P|B|C]|$9|Q|A|R|B|C]|$9|S|A|T|B|C]|$9|U|A|V|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|W|8|@$9|X|A|Y|B|C]|$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|11|8|@]|D|@]|E|$]]]|I|$]]

<code>DDX_Control()</code> does <code>SubclassWindow()</code> under the hood. <code>SubclassDlgItem</code> is a shortcut for <code>SubclassWindow(GetDlgITem())</code>. Usually (broad generalisation here) the people using <code>SubclassWindow</code> are the ones who picked up that habit before <code>DDX_Control</code> existed (pre-1995 or so?) and never really got into MFC-mode, or people who copy and paste their programs together from blog snippets left and right.
So, use <code>DDX_Control()</code> for clarity, although it will technically not make a difference if you use <code>SubclassDlgItem()</code>.

blocks|key|2538641|text|放在资源编辑器对话框中的窗口是使用CreateWindow(Ex)创建的，第一个参数设置为在.rc文件中指定的类名。然后，DDX_机制将这个实例化的窗口与DoDataExchange()中的对话框类成员关联起来。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2538642|MFC是Win32之上的一层，但是MFC开发并不能完全将您与Win32隔离开来。它更像是一堆类和方法，去掉了MFC的一些繁琐工作，并提供了某种形式的面向对象。MFC对象的方法并不是真正做实际工作的方法，框架的大部分工作都是在幕后进行的，除非显式地连接起来，否则不会通知“上层”(即MFC对象)。Create()就是这样一个方法，只有当你想手动创建一个控件时，它才会出现在那里，当创建对象时，它不会被MFC调用。(这是一种概括，因为有时确实如此，但这超出了本文的讨论范围)。|2538643|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

The windows you put on a dialog with the resource editor are created using CreateWindow(Ex) with the first argument set to the class name that is specified in the .rc file. The DDX_ mechanism then associates this instantiated window with the dialog class member in DoDataExchange().

MFC is a layer over Win32 but MFC development doesn't completely shield you from Win32. It's more like a bunch of classes and methods that take away some of the drudgery of MFC and provide some form of object-orientedness. The methods of MFC object aren't the ones that are doing the real work, and much of the framework does things under the hood and doesn't notify the 'upper layer' (i.e., MFC objects) unless that is explicitly hooked up. Create() is such a method that is only there if you want to manually create a control, it's not called by MFC when the object is created. (this is a generalization because sometimes it is, but that's outside of the scope of this discussion).

blocks|key|54557|text|对于您放在资源编辑器对话框中的控件，使用DDX_Control：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|54558|class+CMyDlg+:+public+CDialogEx
{

protected:
++++virtual+void+DoDataExchange(CDataExchange*+pDX);+//+DDX/DDV+support

public:
++++CRichEditCtrl+m_Rich;
};

void+CMyDlg::DoDataExchange(CDataExchange*+pDX)
{
++++CDialogEx::DoDataExchange(pDX);
++++DDX_Control(pDX,+IDC_RICHEDIT1,+m_Rich);
}|code-block|syntax|javascript|54559|手动创建的控件的2>：|54560|CRichEditCtrl+m_Rich;++m_Rich.Create(...);++m_Rich.SubclassDlgItem(IDC_RICH,+this));|offset|length|style|CODE|54561|entityMap^0|0|0|0|0|2C|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|T|8|@$K|U|L|V|M|N]]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

1> For controls that you put on a dialog with the resource editor, used DDX_Control:

<pre><code>class CMyDlg : public CDialogEx
{

protected:
 virtual void DoDataExchange(CDataExchange* pDX); // DDX/DDV support

public:
 CRichEditCtrl m_Rich;
};

void CMyDlg::DoDataExchange(CDataExchange* pDX)
{
 CDialogEx::DoDataExchange(pDX);
 DDX_Control(pDX, IDC_RICHEDIT1, m_Rich);
}
</code></pre>

2> For controls that create manually: 

<code>CRichEditCtrl m_Rich;
 m_Rich.Create(...);
 m_Rich.SubclassDlgItem(IDC_RICH, this));</code>

We layout dialogs using the resource editor. So say I have a RichEditCtrl called IDC_RICH. And I want to link it to an instance of a custom class <code>CMyRichEditCtrl : CRichEditCtrl</code>, without losing the ability to set properties on it in resource editor.

What's the right way? You can certainly get some functionality by creating a DDX-linked variable, and changing the type to <code>CMyRichEditCtrl</code>. But in some cases I see people calling code like:

<pre><code>m_Rich.SubclassDlgItem(IDC_RICH, this));
</code></pre>

What's the difference?

EDIT: One problem I'm seeing is that when I override Create(Ex) methods, they don't get called. It's kind of like the control is already created by the time my object gets linked to the resource identifier, pehaps?

What's the correct way to create a subclass of a MFC control?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

我们使用资源编辑器来布局对话框。假设我有一个名为IDC_RICH的RichEditCtrl。我想把它链接到一个自定义类CMyRichEditCtrl : CRichEditCtrl的实例上，而不会失去在资源编辑器中设置它的属性的能力。正确的方法是什么？您当然可以通过创建一个与DDX链接的变量并将类型更改为CMyRich...

问创建MFC控件的子类的正确方法是什么？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问创建MFC控件的子类的正确方法是什么？EN