[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fU7VE3gKd1dD-bBHXcvcz8UTSdYSEYjpyigbRoh3VHSo":3,"$fJU-4tot_gC5fDkujNeoE-cGsdMy5V_KcdUXLuAnTFgw":15,"$fhoS8FDp9H0Pse_HVhmNJiue_mcJG8iq4UV9RUm22jwE":423},{"slug":4,"title":5,"description":6,"content":7,"content_html":8,"pub_date":9,"tags":10,"draft":14},"mfc-cstring-wparam","MFC 中 CString 与 WPARAM 之间的转换","详解 MFC 消息传递中 CString 无法直接强转为 WPARAM 的原因，以及两种正确的转换方案，并介绍结构体指针传递的正确姿势。","# MFC 中 CString 与 WPARAM 之间的转换\n\n在 MFC 编程中，经常需要通过 Windows 消息（`SendMessage`\u002F`PostMessage`）传递字符串数据。`CString` 是 MFC 的核心字符串类，而 `WPARAM`（`LPARAM`）本质上是整数类型，两者之间的转换有很多细节需要注意。\n\n## MFC CString 内存布局\n\n`CString`（`CStringT` 模板的特化）的内存布局经过精心设计，支持引用计数和写时复制（COW，Copy-On-Write）。\n\n在内存中，`CString` 对象本身只是一个指针，指向一个带有头部信息的字符缓冲区：\n\n```\nCString 对象（4\u002F8 字节指针）\n    │\n    ▼\n[StringData 头部]\n  nRefs:      引用计数（负数表示锁定）\n  nDataLength: 实际字符串长度\n  nAllocLength: 分配的缓冲区长度\n  nCrtAllocBytes: CRT 分配大小\n[字符数据区]\n  字符 0, 1, 2, ...  \u003C── m_pszData 指向这里\n  NUL（终止符）\n```\n\n关键点：`CString::GetString()`（或强制转换 `(LPCTSTR)str`）返回的是**字符数据区的起始地址**，而不是 `CString` 对象本身的地址。\n\n```cpp\nCString str = _T(\"Hello\");\nLPCTSTR p1 = str.GetString();   \u002F\u002F 指向字符数据\nLPCTSTR p2 = (LPCTSTR)str;      \u002F\u002F 等价\n\u002F\u002F p1 == p2 == 字符数据的起始地址\n```\n\n## WPARAM 的本质（UINT_PTR）\n\n`WPARAM` 定义为：\n\n```cpp\ntypedef UINT_PTR WPARAM;\ntypedef LONG_PTR LPARAM;\n```\n\n其中 `UINT_PTR` 在 32 位系统上是 `unsigned int`（4 字节），在 64 位系统上是 `unsigned __int64`（8 字节）。\n\n它足够宽以容纳一个指针，这是 Windows API 兼容性设计的一部分。\n\n## 直接转换的危险\n\n### 危险 1：传递临时对象的指针\n\n```cpp\n\u002F\u002F ❌ 极度危险！\nvoid BadSend(HWND hwnd) {\n    CString str = _T(\"Hello\");\n    \u002F\u002F str 在函数栈上，返回后销毁\n    \u002F\u002F 但 SendMessage 是同步的，这里可能侥幸可以\n    SendMessage(hwnd, WM_USER_STR, 0, (LPARAM)(LPCTSTR)str);\n}\n\n\u002F\u002F ❌ 更危险：PostMessage（异步）\nvoid VeryBadSend(HWND hwnd) {\n    CString str = _T(\"Hello\");\n    PostMessage(hwnd, WM_USER_STR, 0, (LPARAM)(LPCTSTR)str);\n    \u002F\u002F 函数返回，str 销毁，接收方处理时是悬空指针！\n}\n```\n\n### 危险 2：直接传 CString 对象指针\n\n```cpp\n\u002F\u002F ❌ 绕过 CString 接口直接传对象指针，接收方用法不统一\nCString* pStr = new CString(_T(\"Hello\"));\nPostMessage(hwnd, WM_USER_STR, 0, (LPARAM)pStr);\n\u002F\u002F 接收方需要知道这是 CString*，而非 LPCTSTR\n\u002F\u002F 且必须 delete，否则内存泄漏\n```\n\n虽然传 `CString*` 技术上可行，但混用裸指针和智能指针会增加维护负担。\n\n### 危险 3：COW 引发的意外\n\n```cpp\n\u002F\u002F ❌ COW 潜在问题\nCString original = _T(\"Hello\");\nCString copy = original;  \u002F\u002F 浅拷贝，共享缓冲区\n\n\u002F\u002F 传递 copy 的 LPCTSTR\nSendMessage(hwnd, WM_USER_STR, 0, (LPARAM)(LPCTSTR)copy);\n\n\u002F\u002F 如果接收方在另一个线程修改了 copy（通过某种方式），\n\u002F\u002F COW 的写时拷贝可能在错误时机发生\n```\n\n## 正确的临时缓冲方案\n\n### 方案一：SendMessage + 接收方提供缓冲区\n\n这是最传统的 Win32 风格，接收方分配缓冲区，发送方填充：\n\n```cpp\n#define WM_GET_TITLE (WM_USER + 1)\n\n\u002F\u002F 发送方：提供缓冲区，SendMessage 等待填充\nTCHAR buffer[256] = {0};\nSendMessage(hwnd, WM_GET_TITLE, (WPARAM)256, (LPARAM)buffer);\nCString title = buffer;\n\n\u002F\u002F 接收方：填充缓冲区\ncase WM_GET_TITLE: {\n    UINT bufSize = (UINT)wParam;\n    LPTSTR pBuf = (LPTSTR)lParam;\n    CString myTitle = _T(\"My Application\");\n    _tcsncpy_s(pBuf, bufSize, myTitle, _TRUNCATE);\n    return 0;\n}\n```\n\n### 方案二：动态分配 + 所有权转移（PostMessage）\n\n```cpp\n#define WM_PUSH_STRING (WM_USER + 2)\n\n\u002F\u002F 发送方：在堆上分配 CString，转移所有权\nvoid SendStringAsync(HWND hwnd, const CString& str) {\n    CString* pStr = new CString(str);  \u002F\u002F 堆上副本\n    \n    if (!PostMessage(hwnd, WM_PUSH_STRING, 0, (LPARAM)pStr)) {\n        delete pStr;  \u002F\u002F 入队失败，自己释放\n        \u002F\u002F 处理错误\n    }\n    \u002F\u002F 所有权已转移，不再访问 pStr\n}\n\n\u002F\u002F 接收方：接管所有权，处理完 delete\ncase WM_PUSH_STRING: {\n    CString* pStr = reinterpret_cast\u003CCString*>(lParam);\n    if (!pStr) return 0;\n    \n    \u002F\u002F 使用字符串\n    SetWindowText(*pStr);\n    \n    delete pStr;  \u002F\u002F 释放内存\n    return 0;\n}\n```\n\n### 方案三：WM_COPYDATA（最安全，适合跨进程）\n\n```cpp\n#define MY_WM_COPYDATA_STRING 1\n\n\u002F\u002F 发送方\nvoid SendStringViaCopyData(HWND hwndTarget, HWND hwndSelf, const CString& str) {\n    \u002F\u002F 准备 COPYDATASTRUCT\n    COPYDATASTRUCT cds;\n    cds.dwData = MY_WM_COPYDATA_STRING;\n    cds.cbData = (str.GetLength() + 1) * sizeof(TCHAR);\n    cds.lpData = (PVOID)(LPCTSTR)str;\n    \n    \u002F\u002F SendMessage 是同步的，lpData 在函数返回前安全\n    SendMessage(hwndTarget, WM_COPYDATA, (WPARAM)hwndSelf, (LPARAM)&cds);\n    \u002F\u002F 注意：WM_COPYDATA 只能用 SendMessage，不能用 PostMessage\n}\n\n\u002F\u002F 接收方\ncase WM_COPYDATA: {\n    COPYDATASTRUCT* pCds = reinterpret_cast\u003CCOPYDATASTRUCT*>(lParam);\n    if (pCds->dwData == MY_WM_COPYDATA_STRING) {\n        CString received((LPCTSTR)pCds->lpData, \n                          pCds->cbData \u002F sizeof(TCHAR) - 1);\n        \u002F\u002F 使用 received...\n    }\n    return TRUE;\n}\n```\n\n`WM_COPYDATA` 的优点：系统自动处理数据复制，不需要手动 `new`\u002F`delete`，跨进程也安全。\n\n## SendMessage vs PostMessage 差异\n\n| 特性 | SendMessage | PostMessage |\n|------|-------------|-------------|\n| 执行方式 | 同步（等待消息处理完成） | 异步（立即返回） |\n| 返回值 | 消息处理函数的返回值 | 是否成功入队（BOOL） |\n| 数据生命周期 | 由调用方控制（在函数返回前安全） | 必须确保接收方处理时数据有效 |\n| 局部变量 | 可以传局部变量地址（同步保证安全） | 不能传局部变量地址！ |\n| 死锁风险 | 有（跨线程相互等待） | 无（异步） |\n| 跨进程 | 支持（注意指针在对方进程无意义） | 支持有限 |\n\n**SendMessage 传局部变量的正确用法：**\n\n```cpp\nvoid SendLocalString(HWND hwnd) {\n    CString localStr = _T(\"This is local\");\n    \n    \u002F\u002F ✅ OK：SendMessage 是同步的\n    \u002F\u002F 函数在 SendMessage 返回之前不会结束，\n    \u002F\u002F localStr 在接收方处理时依然有效\n    SendMessage(hwnd, WM_USER_STR, 0, (LPARAM)(LPCTSTR)localStr);\n    \n    \u002F\u002F 此时 SendMessage 已返回，localStr 销毁\n}\n```\n\n## 示例代码：完整的线程间通信\n\n```cpp\n\u002F\u002F 消息定义\n#define WM_UI_UPDATE_TEXT (WM_USER + 10)\n\n\u002F\u002F ========== 工作线程 ==========\nUINT WorkerThread(LPVOID pParam) {\n    HWND hwndMain = (HWND)pParam;\n    \n    for (int i = 0; i \u003C 10; i++) {\n        \u002F\u002F 模拟耗时操作\n        Sleep(1000);\n        \n        \u002F\u002F 生成结果字符串\n        CString result;\n        result.Format(_T(\"Step %d completed\"), i + 1);\n        \n        \u002F\u002F 堆上副本，PostMessage 异步发送\n        CString* pResult = new CString(result);\n        if (!PostMessage(hwndMain, WM_UI_UPDATE_TEXT, i, (LPARAM)pResult)) {\n            delete pResult;\n        }\n    }\n    \n    \u002F\u002F 发送完成通知（无额外数据）\n    PostMessage(hwndMain, WM_UI_UPDATE_TEXT, -1, 0);\n    return 0;\n}\n\n\u002F\u002F ========== 主线程消息处理 ==========\nLRESULT CMainDlg::OnUpdateText(WPARAM wParam, LPARAM lParam) {\n    int step = (int)wParam;\n    \n    if (step == -1) {\n        \u002F\u002F 完成\n        SetDlgItemText(IDC_STATUS, _T(\"All done!\"));\n        return 0;\n    }\n    \n    \u002F\u002F 接管 CString 所有权\n    CString* pText = reinterpret_cast\u003CCString*>(lParam);\n    if (pText) {\n        SetDlgItemText(IDC_STATUS, *pText);\n        delete pText;\n    }\n    \n    return 0;\n}\n```\n\n消息映射：\n```cpp\nBEGIN_MESSAGE_MAP(CMainDlg, CDialog)\n    ON_MESSAGE(WM_UI_UPDATE_TEXT, &CMainDlg::OnUpdateText)\nEND_MESSAGE_MAP()\n```\n\n## 内存安全总结\n\n1. **PostMessage 异步，不能传局部变量或栈上数据**——使用 `new` 在堆上分配，接收方负责 `delete`。\n\n2. **SendMessage 同步，可以传局部变量**——但仅限同线程或跨线程 SendMessage 不会死锁的场景。\n\n3. **所有权协议**：`new` 出来的数据，如果通过 `PostMessage` 发出，所有权就转移了，发送方不再访问也不再释放。\n\n4. **PostMessage 失败时必须自己 delete**——检查返回值！\n\n5. **跨进程用 WM_COPYDATA**——进程边界两侧指针指向不同地址空间，唯一安全的传字符串方式是 `WM_COPYDATA`。\n\n6. **优先考虑 `WM_COPYDATA`**——它由系统管理数据复制，无需手动 `new`\u002F`delete`，是最健壮的方式（但只能用 `SendMessage`）。\n","\u003Ch1>MFC 中 CString 与 WPARAM 之间的转换\u003C\u002Fh1>\n\u003Cp>在 MFC 编程中，经常需要通过 Windows 消息（\u003Ccode>SendMessage\u003C\u002Fcode>\u002F\u003Ccode>PostMessage\u003C\u002Fcode>）传递字符串数据。\u003Ccode>CString\u003C\u002Fcode> 是 MFC 的核心字符串类，而 \u003Ccode>WPARAM\u003C\u002Fcode>（\u003Ccode>LPARAM\u003C\u002Fcode>）本质上是整数类型，两者之间的转换有很多细节需要注意。\u003C\u002Fp>\n\u003Ch2 id=\"mfc-cstring-内存布局\">MFC CString 内存布局\u003C\u002Fh2>\n\u003Cp>\u003Ccode>CString\u003C\u002Fcode>（\u003Ccode>CStringT\u003C\u002Fcode> 模板的特化）的内存布局经过精心设计，支持引用计数和写时复制（COW，Copy-On-Write）。\u003C\u002Fp>\n\u003Cp>在内存中，\u003Ccode>CString\u003C\u002Fcode> 对象本身只是一个指针，指向一个带有头部信息的字符缓冲区：\u003C\u002Fp>\n\u003Cpre>\u003Ccode>CString 对象（4\u002F8 字节指针）\n    │\n    ▼\n[StringData 头部]\n  nRefs:      引用计数（负数表示锁定）\n  nDataLength: 实际字符串长度\n  nAllocLength: 分配的缓冲区长度\n  nCrtAllocBytes: CRT 分配大小\n[字符数据区]\n  字符 0, 1, 2, ...  <── m_pszData 指向这里\n  NUL（终止符）\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>关键点：\u003Ccode>CString::GetString()\u003C\u002Fcode>（或强制转换 \u003Ccode>(LPCTSTR)str\u003C\u002Fcode>）返回的是\u003Cstrong>字符数据区的起始地址\u003C\u002Fstrong>，而不是 \u003Ccode>CString\u003C\u002Fcode> 对象本身的地址。\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-cpp\">CString str = _T("Hello");\nLPCTSTR p1 = str.GetString();   \u002F\u002F 指向字符数据\nLPCTSTR p2 = (LPCTSTR)str;      \u002F\u002F 等价\n\u002F\u002F p1 == p2 == 字符数据的起始地址\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch2 id=\"wparam-的本质-uint_ptr\">WPARAM 的本质（UINT_PTR）\u003C\u002Fh2>\n\u003Cp>\u003Ccode>WPARAM\u003C\u002Fcode> 定义为：\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-cpp\">typedef UINT_PTR WPARAM;\ntypedef LONG_PTR LPARAM;\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>其中 \u003Ccode>UINT_PTR\u003C\u002Fcode> 在 32 位系统上是 \u003Ccode>unsigned int\u003C\u002Fcode>（4 字节），在 64 位系统上是 \u003Ccode>unsigned __int64\u003C\u002Fcode>（8 字节）。\u003C\u002Fp>\n\u003Cp>它足够宽以容纳一个指针，这是 Windows API 兼容性设计的一部分。\u003C\u002Fp>\n\u003Ch2 id=\"直接转换的危险\">直接转换的危险\u003C\u002Fh2>\n\u003Ch3 id=\"危险-1-传递临时对象的指针\">危险 1：传递临时对象的指针\u003C\u002Fh3>\n\u003Cpre>\u003Ccode class=\"language-cpp\">\u002F\u002F ❌ 极度危险！\nvoid BadSend(HWND hwnd) {\n    CString str = _T("Hello");\n    \u002F\u002F str 在函数栈上，返回后销毁\n    \u002F\u002F 但 SendMessage 是同步的，这里可能侥幸可以\n    SendMessage(hwnd, WM_USER_STR, 0, (LPARAM)(LPCTSTR)str);\n}\n\n\u002F\u002F ❌ 更危险：PostMessage（异步）\nvoid VeryBadSend(HWND hwnd) {\n    CString str = _T("Hello");\n    PostMessage(hwnd, WM_USER_STR, 0, (LPARAM)(LPCTSTR)str);\n    \u002F\u002F 函数返回，str 销毁，接收方处理时是悬空指针！\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch3 id=\"危险-2-直接传-cstring-对象指针\">危险 2：直接传 CString 对象指针\u003C\u002Fh3>\n\u003Cpre>\u003Ccode class=\"language-cpp\">\u002F\u002F ❌ 绕过 CString 接口直接传对象指针，接收方用法不统一\nCString* pStr = new CString(_T("Hello"));\nPostMessage(hwnd, WM_USER_STR, 0, (LPARAM)pStr);\n\u002F\u002F 接收方需要知道这是 CString*，而非 LPCTSTR\n\u002F\u002F 且必须 delete，否则内存泄漏\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>虽然传 \u003Ccode>CString*\u003C\u002Fcode> 技术上可行，但混用裸指针和智能指针会增加维护负担。\u003C\u002Fp>\n\u003Ch3 id=\"危险-3-cow-引发的意外\">危险 3：COW 引发的意外\u003C\u002Fh3>\n\u003Cpre>\u003Ccode class=\"language-cpp\">\u002F\u002F ❌ COW 潜在问题\nCString original = _T("Hello");\nCString copy = original;  \u002F\u002F 浅拷贝，共享缓冲区\n\n\u002F\u002F 传递 copy 的 LPCTSTR\nSendMessage(hwnd, WM_USER_STR, 0, (LPARAM)(LPCTSTR)copy);\n\n\u002F\u002F 如果接收方在另一个线程修改了 copy（通过某种方式），\n\u002F\u002F COW 的写时拷贝可能在错误时机发生\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch2 id=\"正确的临时缓冲方案\">正确的临时缓冲方案\u003C\u002Fh2>\n\u003Ch3 id=\"方案一-sendmessage-接收方提供缓冲区\">方案一：SendMessage + 接收方提供缓冲区\u003C\u002Fh3>\n\u003Cp>这是最传统的 Win32 风格，接收方分配缓冲区，发送方填充：\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-cpp\">#define WM_GET_TITLE (WM_USER + 1)\n\n\u002F\u002F 发送方：提供缓冲区，SendMessage 等待填充\nTCHAR buffer[256] = {0};\nSendMessage(hwnd, WM_GET_TITLE, (WPARAM)256, (LPARAM)buffer);\nCString title = buffer;\n\n\u002F\u002F 接收方：填充缓冲区\ncase WM_GET_TITLE: {\n    UINT bufSize = (UINT)wParam;\n    LPTSTR pBuf = (LPTSTR)lParam;\n    CString myTitle = _T("My Application");\n    _tcsncpy_s(pBuf, bufSize, myTitle, _TRUNCATE);\n    return 0;\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch3 id=\"方案二-动态分配-所有权转移-postmessage\">方案二：动态分配 + 所有权转移（PostMessage）\u003C\u002Fh3>\n\u003Cpre>\u003Ccode class=\"language-cpp\">#define WM_PUSH_STRING (WM_USER + 2)\n\n\u002F\u002F 发送方：在堆上分配 CString，转移所有权\nvoid SendStringAsync(HWND hwnd, const CString& str) {\n    CString* pStr = new CString(str);  \u002F\u002F 堆上副本\n    \n    if (!PostMessage(hwnd, WM_PUSH_STRING, 0, (LPARAM)pStr)) {\n        delete pStr;  \u002F\u002F 入队失败，自己释放\n        \u002F\u002F 处理错误\n    }\n    \u002F\u002F 所有权已转移，不再访问 pStr\n}\n\n\u002F\u002F 接收方：接管所有权，处理完 delete\ncase WM_PUSH_STRING: {\n    CString* pStr = reinterpret_cast<CString*>(lParam);\n    if (!pStr) return 0;\n    \n    \u002F\u002F 使用字符串\n    SetWindowText(*pStr);\n    \n    delete pStr;  \u002F\u002F 释放内存\n    return 0;\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch3 id=\"方案三-wm_copydata-最安全-适合跨进程\">方案三：WM_COPYDATA（最安全，适合跨进程）\u003C\u002Fh3>\n\u003Cpre>\u003Ccode class=\"language-cpp\">#define MY_WM_COPYDATA_STRING 1\n\n\u002F\u002F 发送方\nvoid SendStringViaCopyData(HWND hwndTarget, HWND hwndSelf, const CString& str) {\n    \u002F\u002F 准备 COPYDATASTRUCT\n    COPYDATASTRUCT cds;\n    cds.dwData = MY_WM_COPYDATA_STRING;\n    cds.cbData = (str.GetLength() + 1) * sizeof(TCHAR);\n    cds.lpData = (PVOID)(LPCTSTR)str;\n    \n    \u002F\u002F SendMessage 是同步的，lpData 在函数返回前安全\n    SendMessage(hwndTarget, WM_COPYDATA, (WPARAM)hwndSelf, (LPARAM)&cds);\n    \u002F\u002F 注意：WM_COPYDATA 只能用 SendMessage，不能用 PostMessage\n}\n\n\u002F\u002F 接收方\ncase WM_COPYDATA: {\n    COPYDATASTRUCT* pCds = reinterpret_cast<COPYDATASTRUCT*>(lParam);\n    if (pCds->dwData == MY_WM_COPYDATA_STRING) {\n        CString received((LPCTSTR)pCds->lpData, \n                          pCds->cbData \u002F sizeof(TCHAR) - 1);\n        \u002F\u002F 使用 received...\n    }\n    return TRUE;\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Ccode>WM_COPYDATA\u003C\u002Fcode> 的优点：系统自动处理数据复制，不需要手动 \u003Ccode>new\u003C\u002Fcode>\u002F\u003Ccode>delete\u003C\u002Fcode>，跨进程也安全。\u003C\u002Fp>\n\u003Ch2 id=\"sendmessage-vs-postmessage-差异\">SendMessage vs PostMessage 差异\u003C\u002Fh2>\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>特性\u003C\u002Fth>\n\u003Cth>SendMessage\u003C\u002Fth>\n\u003Cth>PostMessage\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>执行方式\u003C\u002Ftd>\n\u003Ctd>同步（等待消息处理完成）\u003C\u002Ftd>\n\u003Ctd>异步（立即返回）\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>返回值\u003C\u002Ftd>\n\u003Ctd>消息处理函数的返回值\u003C\u002Ftd>\n\u003Ctd>是否成功入队（BOOL）\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>数据生命周期\u003C\u002Ftd>\n\u003Ctd>由调用方控制（在函数返回前安全）\u003C\u002Ftd>\n\u003Ctd>必须确保接收方处理时数据有效\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>局部变量\u003C\u002Ftd>\n\u003Ctd>可以传局部变量地址（同步保证安全）\u003C\u002Ftd>\n\u003Ctd>不能传局部变量地址！\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>死锁风险\u003C\u002Ftd>\n\u003Ctd>有（跨线程相互等待）\u003C\u002Ftd>\n\u003Ctd>无（异步）\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>跨进程\u003C\u002Ftd>\n\u003Ctd>支持（注意指针在对方进程无意义）\u003C\u002Ftd>\n\u003Ctd>支持有限\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003Cp>\u003Cstrong>SendMessage 传局部变量的正确用法：\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-cpp\">void SendLocalString(HWND hwnd) {\n    CString localStr = _T("This is local");\n    \n    \u002F\u002F ✅ OK：SendMessage 是同步的\n    \u002F\u002F 函数在 SendMessage 返回之前不会结束，\n    \u002F\u002F localStr 在接收方处理时依然有效\n    SendMessage(hwnd, WM_USER_STR, 0, (LPARAM)(LPCTSTR)localStr);\n    \n    \u002F\u002F 此时 SendMessage 已返回，localStr 销毁\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch2 id=\"示例代码-完整的线程间通信\">示例代码：完整的线程间通信\u003C\u002Fh2>\n\u003Cpre>\u003Ccode class=\"language-cpp\">\u002F\u002F 消息定义\n#define WM_UI_UPDATE_TEXT (WM_USER + 10)\n\n\u002F\u002F ========== 工作线程 ==========\nUINT WorkerThread(LPVOID pParam) {\n    HWND hwndMain = (HWND)pParam;\n    \n    for (int i = 0; i < 10; i++) {\n        \u002F\u002F 模拟耗时操作\n        Sleep(1000);\n        \n        \u002F\u002F 生成结果字符串\n        CString result;\n        result.Format(_T("Step %d completed"), i + 1);\n        \n        \u002F\u002F 堆上副本，PostMessage 异步发送\n        CString* pResult = new CString(result);\n        if (!PostMessage(hwndMain, WM_UI_UPDATE_TEXT, i, (LPARAM)pResult)) {\n            delete pResult;\n        }\n    }\n    \n    \u002F\u002F 发送完成通知（无额外数据）\n    PostMessage(hwndMain, WM_UI_UPDATE_TEXT, -1, 0);\n    return 0;\n}\n\n\u002F\u002F ========== 主线程消息处理 ==========\nLRESULT CMainDlg::OnUpdateText(WPARAM wParam, LPARAM lParam) {\n    int step = (int)wParam;\n    \n    if (step == -1) {\n        \u002F\u002F 完成\n        SetDlgItemText(IDC_STATUS, _T("All done!"));\n        return 0;\n    }\n    \n    \u002F\u002F 接管 CString 所有权\n    CString* pText = reinterpret_cast<CString*>(lParam);\n    if (pText) {\n        SetDlgItemText(IDC_STATUS, *pText);\n        delete pText;\n    }\n    \n    return 0;\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>消息映射：\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-cpp\">BEGIN_MESSAGE_MAP(CMainDlg, CDialog)\n    ON_MESSAGE(WM_UI_UPDATE_TEXT, &CMainDlg::OnUpdateText)\nEND_MESSAGE_MAP()\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch2 id=\"内存安全总结\">内存安全总结\u003C\u002Fh2>\n\u003Col>\n\u003Cli>\n\u003Cp>\u003Cstrong>PostMessage 异步，不能传局部变量或栈上数据\u003C\u002Fstrong>——使用 \u003Ccode>new\u003C\u002Fcode> 在堆上分配，接收方负责 \u003Ccode>delete\u003C\u002Fcode>。\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>SendMessage 同步，可以传局部变量\u003C\u002Fstrong>——但仅限同线程或跨线程 SendMessage 不会死锁的场景。\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>所有权协议\u003C\u002Fstrong>：\u003Ccode>new\u003C\u002Fcode> 出来的数据，如果通过 \u003Ccode>PostMessage\u003C\u002Fcode> 发出，所有权就转移了，发送方不再访问也不再释放。\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>PostMessage 失败时必须自己 delete\u003C\u002Fstrong>——检查返回值！\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>跨进程用 WM_COPYDATA\u003C\u002Fstrong>——进程边界两侧指针指向不同地址空间，唯一安全的传字符串方式是 \u003Ccode>WM_COPYDATA\u003C\u002Fcode>。\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>优先考虑 \u003Ccode>WM_COPYDATA\u003C\u002Fcode>\u003C\u002Fstrong>——它由系统管理数据复制，无需手动 \u003Ccode>new\u003C\u002Fcode>\u002F\u003Ccode>delete\u003C\u002Fcode>，是最健壮的方式（但只能用 \u003Ccode>SendMessage\u003C\u002Fcode>）。\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Fol>\n","2022-11-25",[11,12,13],"mfc","cpp","windows",false,[16,29,40,52,62,69,76,83,90,97,107,116,126,135,143,151,160,169,178,188,195,204,210,217,223,232,239,246,254,264,273,282,292,302,312,320,330,341,350,359,367,373,381,389,392,400,408,415],{"slug":17,"title":18,"description":19,"pub_date":20,"tags":21,"draft":14,"word_count":28},"ide-skills-guide","Agent Skills 完全指南：21 款第三方 Skill 深度评测与使用心得","全面评测 21 款第三方 Agent Skills，涵盖 Vue 生态、前端设计、构建工具、实用工具四大分类。从安装配置到实际使用场景，带你了解每个 Skill 的功能特点、最佳实践与使用心得。","2026-06-15",[22,23,24,25,26,27],"agent","skills","AI","效率工具","前端","Vue",4169,{"slug":30,"title":31,"description":32,"pub_date":33,"tags":34,"draft":14,"word_count":39},"linux-kernel-skeleton-struct-funcptr-container_of","Linux 内核骨架：struct、函数指针与 container_of","读懂 Linux 内核源码的三件套：巨大的 struct 组合代替继承、函数指针表实现虚派发、container_of 宏从嵌入成员找回完整对象。","2026-05-09",[35,36,37,38],"linux","kernel","C","container_of",1369,{"slug":41,"title":42,"description":43,"pub_date":44,"tags":45,"draft":14,"word_count":51},"astro-complete-guide-2025","Astro 5 深度剖析：Islands 架构原理、构建优化与 Cloudflare Workers 边缘部署","从编译器视角解析 Astro 5 的 Islands 架构实现原理，Content Layer API 的 Vite 插件机制，Server Islands 的流式渲染，以及如何在 Cloudflare Workers + D1 边缘环境下榨干性能。","2026-05-08",[46,47,48,49,50],"astro","frontend","cloudflare","performance","architecture",3663,{"slug":53,"title":54,"description":55,"pub_date":56,"tags":57,"draft":14,"word_count":61},"llm-prompt-engineering","Prompt Engineering 实战：让 LLM 真正听话的技巧","System prompt 怎么写、Few-shot 怎么设计、Chain-of-Thought 原理，以及常见失败模式和调试方法。","2026-05-03",[58,59,60],"ai","llm","工程实践",1723,{"slug":63,"title":64,"description":65,"pub_date":56,"tags":66,"draft":14,"word_count":68},"rag-system-design","RAG 系统设计：从 naive 到 production-ready","Retrieval-Augmented Generation 不只是「向量数据库 + LLM」，分块策略、召回质量、重排序、缓存才是工程核心。",[58,67,59,60],"rag",1613,{"slug":70,"title":71,"description":72,"pub_date":56,"tags":73,"draft":14,"word_count":75},"git-advanced-workflow","Git 进阶工作流：rebase、cherry-pick、bisect 的正确使用","merge 会了，但 rebase 总搞错？bisect 找 bug 提交？interactive rebase 整理历史？这篇一次说清楚。",[74,60],"git",1396,{"slug":77,"title":78,"description":79,"pub_date":56,"tags":80,"draft":14,"word_count":82},"docker-practical-guide","Docker 实战：从会用到用好","会 docker run 不够，Dockerfile 最佳实践、多阶段构建、Compose 编排、镜像瘦身才是日常真正需要的。",[81,35,60],"docker",1268,{"slug":84,"title":85,"description":86,"pub_date":56,"tags":87,"draft":14,"word_count":89},"anthropics-skills-guide","anthropics\u002Fskills：Anthropic 官方 Agent Skills 仓库解析","Anthropic 官方开源的 Agent Skills 标准仓库，127k stars，解析 SKILL.md 规范、17 个示例 skill 的设计模式，以及如何在 Claude Code \u002F Claude.ai \u002F API 中使用",[58,88,22,23],"Claude",2090,{"slug":91,"title":92,"description":93,"pub_date":56,"tags":94,"draft":14,"word_count":96},"karpathy-claude-code-guidelines","Karpathy 的 LLM 编码批评与 CLAUDE.md 最佳实践","基于 Andrej Karpathy 对 LLM 编程助手的观察，forrestchang 提炼出一个 CLAUDE.md 文件，4 条原则解决 AI 编码的典型失控问题：乱猜假设、过度设计、乱改代码、目标不清",[58,88,95,60],"Claude Code",2699,{"slug":98,"title":99,"description":100,"pub_date":56,"tags":101,"draft":14,"word_count":106},"typescript-advanced-patterns","TypeScript 高级模式：让类型系统为你工作","基础 TS 会了但类型总是 any？条件类型、映射类型、模板字面量类型、infer 关键字才是 TS 的真正威力。",[102,103,104,105],"typescript","类型系统","前端工程","高级模式",1419,{"slug":108,"title":109,"description":110,"pub_date":56,"tags":111,"draft":14,"word_count":115},"linux-performance-tuning","Linux 性能调优实战：从 top 到 perf 的完整工具链","遇到性能问题不知道从哪下手？这篇建立系统化的排查思路，从 CPU\u002F内存\u002FIO\u002F网络逐层分析。",[35,112,113,114],"性能","运维","系统编程",1524,{"slug":117,"title":118,"description":119,"pub_date":56,"tags":120,"draft":14,"word_count":125},"python-functional-programming","Python 函数式编程：map\u002Ffilter\u002Freduce 之外","Python 不是纯函数式语言，但 functools、itertools、偏函数、闭包这些工具用好了能让代码简洁一个量级。",[121,122,123,124],"python","函数式","闭包","装饰器",1867,{"slug":127,"title":128,"description":129,"pub_date":56,"tags":130,"draft":14,"word_count":134},"python-oop-guide","Python 面向对象：__init__ 之外你需要知道的","Python OOP 不只是 class + __init__，魔术方法、描述符、元类才是真正的武器。",[121,131,132,133],"OOP","面向对象","魔术方法",1792,{"slug":136,"title":137,"description":138,"pub_date":56,"tags":139,"draft":14,"word_count":142},"python-data-structures","Python 内置数据结构深度解析","list、dict、set、tuple 不只是数据容器，搞懂它们的底层实现和时间复杂度，才能写出高性能 Python。",[121,140,112,141],"数据结构","算法",1517,{"slug":144,"title":145,"description":146,"pub_date":56,"tags":147,"draft":14,"word_count":150},"python-basics-quick-start","Python 快速上手：写给有编程基础的人","已经会其他语言，想快速掌握 Python 的语法特性和思维方式，这篇是捷径。",[121,148,149],"入门","基础",1607,{"slug":152,"title":153,"description":154,"pub_date":56,"tags":155,"draft":14,"word_count":159},"python-dataclass-pydantic","Python dataclass vs Pydantic：数据类选型指南","dataclass 是标准库的轻量选择，Pydantic v2 是带验证的重武器，什么时候用哪个，这篇说清楚。",[121,156,157,158],"dataclass","pydantic","数据验证",1323,{"slug":161,"title":162,"description":163,"pub_date":56,"tags":164,"draft":14,"word_count":168},"python-asyncio-practical","Python asyncio 实战：从回调地狱到协程优雅","asyncio 是 Python 异步编程的核心，搞懂 event loop、Task、gather 这些概念才能写出真正高效的异步代码。",[121,165,166,167],"asyncio","并发","网络编程",1258,{"slug":170,"title":171,"description":172,"pub_date":56,"tags":173,"draft":14,"word_count":177},"python-type-hints-guide","Python 类型注解完全指南：从入门到实践","Python 3.5+ 引入类型注解，配合 mypy\u002Fpyright 让 Python 也能享受静态类型检查的好处。",[121,174,175,176],"typescript-style","type-hints","工具链",1102,{"slug":179,"title":180,"description":181,"pub_date":182,"tags":183,"draft":14,"word_count":187},"pwa-install-update-button","PWA 踩坑：为什么安装按钮从来不出现","从 beforeinstallprompt 到 Service Worker waiting，把 PWA 的安装与更新提示真正做对","2026-05-02",[184,185,186],"pwa","javascript","web",1683,{"slug":189,"title":190,"description":191,"pub_date":192,"tags":193,"draft":14,"word_count":194},"openclaw-vs-hermes-agent","OpenClaw vs Hermes Agent：两个本地优先 Agent 的设计差异","OpenClaw（Novita AI）和 Hermes Agent（Nous Research）都是本地运行的个人 AI Agent，但在记忆系统、技能学习、运行环境和模型生态上走了不同的路。深入对比两种架构的核心差异。","2026-05-01",[58,22,59],1679,{"slug":196,"title":197,"description":198,"pub_date":192,"tags":199,"draft":14,"word_count":203},"cpp-random-design-patterns","C++ 设计模式实战：RAII、观察者、工厂","用现代 C++（C++17\u002F20）实现三种高频设计模式：RAII 资源管理、观察者模式事件系统、工厂模式插件架构。每种模式给出问题场景、实现代码和真实工程案例。",[12,200,201,202],"设计模式","c++17","工程",2613,{"slug":205,"title":206,"description":207,"pub_date":192,"tags":208,"draft":14,"word_count":209},"data-structures-fundamentals","数据结构基础：从数组到红黑树","系统梳理常用数据结构的核心原理、时间复杂度和适用场景。数组、链表、栈、队列、哈希表、二叉树、堆、图，每种结构附实现要点和 C++ 代码片段。",[140,141,12,149],3004,{"slug":211,"title":212,"description":213,"pub_date":214,"tags":215,"draft":14,"word_count":216},"ai-agent-what-is","什么是 AI Agent？从 LLM 到自主执行","LLM 本身是无状态问答机，Agent 是什么让它’动’起来的？本文深入解析 Agent 的四个核心能力、ReAct 框架、工具调用原理，以及主流框架横向对比。","2026-04-30",[58,22,59],2116,{"slug":218,"title":219,"description":220,"pub_date":214,"tags":221,"draft":14,"word_count":222},"ai-agent-memory","AI Agent 的记忆系统：从上下文窗口到长期记忆","深入拆解 AI Agent 的四种记忆类型、上下文窗口压缩策略、RAG 向量检索原理，以及三种典型失败模式和工程选型建议。",[58,22,67],2052,{"slug":224,"title":225,"description":226,"pub_date":214,"tags":227,"draft":14,"word_count":231},"network-proxy-vpn-guide","代理与翻墙技术原理：从 HTTP 代理到现代协议","深入解析代理与 VPN 的本质区别，梳理从 SOCKS5 到 Shadowsocks、V2Ray\u002FXray、Hysteria2 的协议演进，以及机场订阅的技术本质。",[228,229,230],"网络","代理","协议",2148,{"slug":233,"title":234,"description":235,"pub_date":214,"tags":236,"draft":14,"word_count":150},"algorithm-binary-search","二分查找：永远写不对？记住这个模板","彻底搞清楚二分查找的边界问题：闭区间和左闭右开两套模板、三道经典 LeetCode 题目完整 C++ 实现，以及二分答案的进阶思路。",[141,237,238,12],"二分查找","leetcode",{"slug":240,"title":241,"description":242,"pub_date":214,"tags":243,"draft":14,"word_count":245},"algorithm-sliding-window","滑动窗口算法：从暴力到 O(n) 的思维跃迁","系统讲解滑动窗口算法的核心模板、适用题型，配合三道经典 LeetCode 题目的完整 C++ 实现，彻底理解双指针收缩思路。",[141,244,238,12],"滑动窗口",1943,{"slug":247,"title":248,"description":249,"pub_date":214,"tags":250,"draft":14,"word_count":253},"network-clash-config","Clash \u002F Mihomo 配置详解：规则、策略组与分流","深入解析 Clash\u002FMihomo 的核心配置结构，包括代理节点、策略组类型、规则优先级、DNS fake-ip 模式，以及一份实用的完整配置模板。",[228,251,229,252],"clash","配置",1292,{"slug":255,"title":256,"description":257,"pub_date":258,"tags":259,"draft":14,"word_count":263},"hid-hotplug","HID 设备热插拔检测：从 udev 到 node-hid","在 Linux 上用 node-hid + usb 库实现可靠的 USB HID 设备热插拔检测，踩坑记录","2026-04-28",[12,260,35,261,262],"hid","nodejs","electron",2039,{"slug":265,"title":266,"description":267,"pub_date":268,"tags":269,"draft":14,"word_count":272},"electron-ipc-types","Electron IPC 类型安全：从 any 到完全类型化","用 TypeScript 泛型封装 Electron IPC，彻底消灭 any，preload 契约集中管理","2026-04-25",[262,102,270,271],"ipc","vue",1446,{"slug":274,"title":275,"description":276,"pub_date":277,"tags":278,"draft":14,"word_count":281},"element-plus-popover-hide","手动关闭多个 el-popover（不用 v-model:visible）","通过 ref + Reflect.get 调用 hide() 方法手动关闭 Element Plus Popover，解释 Vue3 Proxy 导致无法直接调用实例方法的原因。","2024-10-25",[271,279,280],"element-plus","vue3",1321,{"slug":283,"title":284,"description":285,"pub_date":286,"tags":287,"draft":14,"word_count":291},"vite-vue3-ts-elementplus-pinia","用 Vite+（vp）从零搭建 Vue3 + TypeScript + Element Plus + Pinia + Vue Router","使用 Vite+ 统一工具链（vp）一条命令搭建 Vue3 全家桶，涵盖按需导入、Pinia store、路由配置，以及常见坑的解决方案。","2024-08-27",[271,288,102,279,289,290],"vite","pinia","vite-plus",1960,{"slug":293,"title":294,"description":295,"pub_date":296,"tags":297,"draft":14,"word_count":301},"cef-lnk2038-iterator-debug-level","CEF LNK2038：解决 _ITERATOR_DEBUG_LEVEL 不匹配错误","分析 CEF（Chromium Embedded Framework）集成时出现的 LNK2038 _ITERATOR_DEBUG_LEVEL 链接错误，从根本原因到解决方案的完整指南。","2024-05-07",[12,298,299,300],"CEF","Visual Studio","链接错误",1509,{"slug":303,"title":304,"description":305,"pub_date":306,"tags":307,"draft":14,"word_count":311},"npm-electron-install-fix","彻底解决 npm 安装 Electron 失败的问题","分析 npm install electron 失败的根本原因（下载二进制超时\u002F被墙），通过国内镜像（npmmirror）彻底解决，并介绍多种备选方案和常见错误排查。","2024-03-01",[262,308,309,310],"npm","前端工具链","国内镜像",1494,{"slug":313,"title":314,"description":315,"pub_date":316,"tags":317,"draft":14,"word_count":319},"git-out-of-memory","解决 git 报错：Fatal: Out of memory, malloc failed","分析 git 大仓库操作时出现 Out of memory malloc failed 的根本原因，通过调整 pack.windowMemory、http.postBuffer 和 git repack 彻底解决。","2024-01-31",[74,35,318],"工具",2244,{"slug":321,"title":322,"description":323,"pub_date":324,"tags":325,"draft":14,"word_count":329},"vmware-tools-install","在 VMware 虚拟机中安装 open-vm-tools 完整指南","详解 VMware Tools 的作用、open-vm-tools 与官方 VMware Tools 的区别，以及在 Ubuntu 虚拟机中安装并生效的完整步骤和常见问题排查。","2023-11-21",[326,35,327,328],"VMware","Ubuntu","虚拟机",2523,{"slug":331,"title":332,"description":333,"pub_date":334,"tags":335,"draft":14,"word_count":340},"load-balancing-algorithms","负载均衡算法完全指南：从轮询到一致性哈希","系统梳理静态与动态负载均衡算法，涵盖轮询、随机、权重、IP Hash、一致性 Hash、最少连接、最快响应等，并对比 Nginx、Dubbo、Spring Cloud LoadBalancer 的实现差异。","2023-11-15",[336,337,338,339],"分布式","负载均衡","Nginx","微服务",1764,{"slug":342,"title":343,"description":344,"pub_date":345,"tags":346,"draft":14,"word_count":349},"win-cw2a-ca2w","ATL 字符串转换：CW2A 与 CA2W 完全指南","详解 ATL 宏 CW2A\u002FCA2W 在 Unicode 与 ANSI 之间的字符串转换用法、头文件依赖、USES_CONVERSION 宏的作用与常见陷阱。","2023-06-09",[12,13,347,348],"ATL","字符串",1665,{"slug":351,"title":352,"description":353,"pub_date":345,"tags":354,"draft":14,"word_count":358},"csharp-sendmessage-cpp","C# 通过 SendMessage 向 C++ 窗口发送消息与字符串","使用 P\u002FInvoke 调用 user32.dll 的 SendMessage，从 C# 发送自定义 WM_USER 消息及字符串指针给 C++ 原生窗口，并在 C++ 侧正确接收和转换。",[355,12,13,356,357],"C#","互操作","PInvoke",1554,{"slug":360,"title":361,"description":362,"pub_date":363,"tags":364,"draft":14,"word_count":366},"win-postmessage-vector","Windows PostMessage 跨线程传递 std::vector 指针","通过 PostMessage 在 Windows 消息队列中传递 std::vector 指针，使用 reinterpret_cast 将指针装入 LPARAM，并在接收方正确释放内存。","2023-05-26",[12,13,365],"WinAPI",1823,{"slug":368,"title":369,"description":370,"pub_date":363,"tags":371,"draft":14,"word_count":372},"exe-dll-single-package","将 EXE 和 DLL 打包成单一可执行文件","介绍两种将 exe 和依赖 dll 打包成单文件的方案：Enigma Virtual Box 和 WinRAR 自解压，适合发布 Windows 桌面程序时简化分发流程。",[13,12,318],1619,{"slug":374,"title":375,"description":376,"pub_date":363,"tags":377,"draft":14,"word_count":380},"cpp-random-mt19937","C++ 现代随机数生成：用 mt19937 彻底告别 rand()","深入讲解为什么 rand() 不够用，以及如何用 C++11 的 \u003Crandom> 库正确生成高质量随机数，涵盖 mt19937、各种分布和线程安全。",[12,378,379],"c++11","random",1549,{"slug":382,"title":383,"description":384,"pub_date":385,"tags":386,"draft":14,"word_count":388},"win-startup-registry","C++ 实现程序开机自启动：注册表方式详解","通过操作 Windows 注册表 Run 键实现程序开机自启动，包括 HKCU 与 HKLM 区别、完整封装代码、工作目录问题和 UAC 权限处理。","2022-12-26",[13,12,387],"registry",1201,{"slug":4,"title":5,"description":6,"pub_date":9,"tags":390,"draft":14,"word_count":391},[11,12,13],1546,{"slug":393,"title":394,"description":395,"pub_date":396,"tags":397,"draft":14,"word_count":399},"duilib-static-build","正确编译 Duilib 静态库：避免 ATL 依赖和链接错误","详解如何用 DuiLib_Static.vcxproj 编译 Duilib 静态库，解决 VARIANT 未定义、Unicode 配置不匹配和 ATL 依赖等常见问题。","2022-08-24",[12,398,13,11],"duilib",2639,{"slug":401,"title":402,"description":403,"pub_date":404,"tags":405,"draft":14,"word_count":407},"mfc-dpi-adaptive","MFC 界面自适应不同分辨率","MFC 对话框程序实现控件和字体随分辨率自动缩放的完整方案，附 DPI Awareness 配置说明","2022-08-17",[11,12,13,406],"dpi",1414,{"slug":409,"title":410,"description":411,"pub_date":412,"tags":413,"draft":14,"word_count":414},"mfc-drag-window","MFC 无标题栏窗口客户区拖动：三种方法对比","MFC 对话框去掉标题栏后如何实现拖动移动窗口，三种方案完整实现与适用场景分析","2022-08-16",[11,12,13],1633,{"slug":416,"title":417,"description":418,"pub_date":419,"tags":420,"draft":14,"word_count":422},"algorithm-number-complement","整数的补数：位运算掩码解法","LeetCode 476 题，用掩码 XOR 实现整数补数，附 C++\u002FPython\u002FJava 三种实现及补数与补码的区别","2021-03-08",[141,421,238],"位运算",1374,[]]