Zoom Windows Meeting SDK 会议聊天开发指南基于 IMeetingChatController 实现收发消息、富文本与文件传输【免费下载链接】knowledge-work-pluginsOpen source repository of plugins primarily intended for knowledge workers to use in Claude Cowork项目地址: https://gitcode.com/GitHub_Trending/kn/knowledge-work-plugins导读本文围绕 Zoom Windows Meeting SDKC 原生 SDK的会议聊天功能系统讲解如何通过IMeetingChatController完成消息发送与接收、富文本格式化加粗、斜体、链接、颜色、文件传输事件监听以及线程化回复。文中代码示例可直接复制到 Visual Studio C 工程中运行并结合本仓库 chat.md 及其配套的 SDK 架构模式、Windows 消息循环 等文档帮助读者快速在 Windows 桌面应用或会议机器人中集成聊天能力。一、聊天功能架构总览Zoom Windows Meeting SDK 将聊天能力封装为IMeetingChatController控制器通过IMeetingService单例获取。整个 SDK 遵循统一的三步模式获取控制器 → 实现事件监听器 → 注册并使用聊天功能正是这一模式的典型代表具体调用链如下IMeetingService └── GetMeetingChatController() → IMeetingChatController ├── SetEvent(IMeetingChatCtrlEvent*) ├── GetChatMessageBuilder() → IChatMsgInfoBuilder ├── SendChatMsgTo(IChatMsgInfo*) └── GetChatStatus()GetMeetingChatController()返回聊天控制器单例同一会议内多次调用返回同一实例SetEvent()注册聊天事件监听器接收消息、状态变更、删除/编辑、文件传输等回调GetChatMessageBuilder()获取消息构造器用于组装带格式的消息体IChatMsgInfoSendChatMsgTo()将构造好的消息发送给全部参会者或指定用户GetChatStatus()查询当前聊天可用状态。该模式在 sdk-architecture-pattern.md 中有完整论述控制器均为通过meetingService-Get[Feature]Controller()获取的单例事件监听器采用观察者模式由 SDK 持有并驱动控制器方法分为动作类如发送与查询类如获取状态两类。理解这一通用公式后音频、视频、录制、共享等 35 个功能控制器的用法都是一致的。二、必需头文件与编译前提实现聊天功能需要包含以下两个头文件#include meeting_service_interface.h #include meeting_service_components/meeting_chat_interface.h其中meeting_service_interface.h提供了IMeetingService及其控制器的获取入口meeting_chat_interface.h定义了IMeetingChatController、IMeetingChatCtrlEvent、IChatMsgInfo、IChatMsgInfoBuilder等聊天相关接口。结合 SKILL.md 中的工程实践经验还需注意两点头文件包含顺序应保证windows.h在最前、cstdint紧随其后再包含 SDK 头文件否则可能出现uint32_t未定义等编译错误必须实现全部纯虚方法IMeetingChatCtrlEvent的每一个纯虚方法都要实现可先写空实现桩否则类无法实例化报error C2259: cannot instantiate abstract class。排查方法可参考 interface-methods.md 中给出的grep 0 SDK/x64/h/*.h定位法。三、Step 1实现聊天事件监听器要接收聊天消息需要继承ZOOMSDK::IMeetingChatCtrlEvent并实现其全部回调。下列代码完整覆盖了消息到达、聊天状态变更、消息删除、消息编辑、会议聊天共享状态变更以及文件传输六大类回调。头文件 MeetingChatEventListener.h#pragma once #include meeting_service_components/meeting_chat_interface.h class MeetingChatEventListener : public ZOOMSDK::IMeetingChatCtrlEvent { public: MeetingChatEventListener() default; virtual ~MeetingChatEventListener() default; // Called when a new chat message arrives virtual void onChatMsgNotification( ZOOMSDK::IChatMsgInfo* chatMsg, const zchar_t* content ) override; // Called when chat privileges change virtual void onChatStatusChangedNotification( ZOOMSDK::ChatStatus* status ) override; // Called when a message is deleted virtual void onChatMsgDeleteNotification( const zchar_t* msgID, ZOOMSDK::SDKChatMessageDeleteType deleteBy ) override; // Called when a message is edited virtual void onChatMessageEditNotification( ZOOMSDK::IChatMsgInfo* chatMsg ) override; // Called when meeting chat sharing status changes virtual void onShareMeetingChatStatusChanged(bool isStart) override; // File transfer callbacks virtual void onFileSendStart(ZOOMSDK::ISDKFileSender* sender) override; virtual void onFileReceived(ZOOMSDK::ISDKFileReceiver* receiver) override; virtual void onFileTransferProgress(ZOOMSDK::SDKFileTransferInfo* info) override; };源文件 MeetingChatEventListener.cpp#include MeetingChatEventListener.h #include iostream using namespace ZOOMSDK; void MeetingChatEventListener::onChatMsgNotification( IChatMsgInfo* chatMsg, const zchar_t* content ) { if (chatMsg content) { // Get sender information unsigned int senderId chatMsg-GetSenderUserId(); const zchar_t* senderName chatMsg-GetSenderDisplayName(); // Get message details const zchar_t* msgContent chatMsg-GetContent(); SDKChatMessageType msgType chatMsg-GetChatMessageType(); std::wcout L[Chat] senderName L: msgContent std::endl; // Check message type switch (msgType) { case SDKChatMessageType_To_All: std::cout (sent to everyone) std::endl; break; case SDKChatMessageType_To_Individual: std::cout (private message) std::endl; break; case SDKChatMessageType_To_WaitingRoomUsers: std::cout (to waiting room) std::endl; break; } // Check if this is a threaded reply const zchar_t* threadId chatMsg-GetThreadID(); if (threadId wcslen(threadId) 0) { std::wcout L Thread ID: threadId std::endl; } } } void MeetingChatEventListener::onChatStatusChangedNotification(ChatStatus* status) { if (status) { std::cout Chat status changed std::endl; // Check what chat privileges are available } } void MeetingChatEventListener::onChatMsgDeleteNotification( const zchar_t* msgID, SDKChatMessageDeleteType deleteBy ) { std::wcout LMessage deleted: msgID std::endl; switch (deleteBy) { case SDKChatMessageDeleteType_By_Self: std::cout (deleted by sender) std::endl; break; case SDKChatMessageDeleteType_By_Host: std::cout (deleted by host) std::endl; break; case SDKChatMessageDeleteType_By_DLP: std::cout (deleted by DLP policy) std::endl; break; } } void MeetingChatEventListener::onChatMessageEditNotification(IChatMsgInfo* chatMsg) { if (chatMsg) { std::wcout LMessage edited: chatMsg-GetContent() std::endl; } } void MeetingChatEventListener::onShareMeetingChatStatusChanged(bool isStart) { std::cout Share meeting chat: (isStart ? started : stopped) std::endl; } void MeetingChatEventListener::onFileSendStart(ISDKFileSender* sender) { std::cout File send started std::endl; } void MeetingChatEventListener::onFileReceived(ISDKFileReceiver* receiver) { std::cout File received std::endl; } void MeetingChatEventListener::onFileTransferProgress(SDKFileTransferInfo* info) { // Handle file transfer progress }要点说明onChatMsgNotification是最核心的回调参数chatMsg携带完整的消息对象content为消息正文通过GetSenderUserId()/GetSenderDisplayName()可获取发送者信息GetChatMessageType()区分消息类型GetThreadID()判断是否为线程内回复文件传输三件套onFileSendStart/onFileReceived/onFileTransferProgress分别对应发送开始、接收到达与进度更新可用于在 UI 上展示上传/下载进度条。四、Step 2初始化聊天控制器聊天控制器必须在进入会议之后获取并完成监听器注册。注册监听器之前先持有控制器指针并检查SetEvent的返回值// Global variables IMeetingChatController* g_chatController nullptr; MeetingChatEventListener* g_chatListener nullptr; void initializeChat(IMeetingService* meetingService) { // Get the chat controller g_chatController meetingService-GetMeetingChatController(); if (!g_chatController) { std::cerr Failed to get chat controller std::endl; return; } // Create and set event listener g_chatListener new MeetingChatEventListener(); SDKError err g_chatController-SetEvent(g_chatListener); if (err ! SDKERR_SUCCESS) { std::cerr Failed to set chat event listener: err std::endl; return; } std::cout Chat controller initialized std::endl; }结合 sdk-architecture-pattern.md 的说明需要注意GetMeetingChatController()在未进入会议时可能返回nullptr控制器可用性与会议状态、SDK App 类型相关监听器生命周期由 SDK 内部维护通常直接new交给 SDK无需手动释放若只想发消息不接收消息SetEvent可以省略但建议始终注册以获取发送结果之外的状态信息见该文档的 Pattern 3: Event Listeners Are Optional。五、Step 3发送聊天消息发送消息的统一流程是GetChatMessageBuilder()获取构造器 → 设置内容、接收者、消息类型 →Build()生成IChatMsgInfo→SendChatMsgTo()发送。5.1 群发消息发送给所有人接收者设为0即代表全体参会者void sendMessageToAll(const wchar_t* message) { if (!g_chatController) return; // Get the message builder IChatMsgInfoBuilder* builder g_chatController-GetChatMessageBuilder(); if (!builder) { std::cerr Failed to get message builder std::endl; return; } // Build the message builder-SetContent(message); builder-SetReceiver(0); // 0 everyone builder-SetMessageType(SDKChatMessageType_To_All); // Build and send IChatMsgInfo* msgInfo builder-Build(); if (msgInfo) { SDKError err g_chatController-SendChatMsgTo(msgInfo); if (err SDKERR_SUCCESS) { std::cout Message sent successfully std::endl; } else { std::cerr Failed to send message: err std::endl; } } }5.2 私聊消息发送给指定用户将SetReceiver参数替换为目标用户的 user ID可在onChatMsgNotification中通过GetSenderUserId()获取或从IMeetingParticipantsController的参会者列表中取得void sendPrivateMessage(unsigned int userId, const wchar_t* message) { if (!g_chatController) return; IChatMsgInfoBuilder* builder g_chatController-GetChatMessageBuilder(); if (!builder) return; builder-SetContent(message); builder-SetReceiver(userId); // Specific user ID builder-SetMessageType(SDKChatMessageType_To_Individual); IChatMsgInfo* msgInfo builder-Build(); if (msgInfo) { SDKError err g_chatController-SendChatMsgTo(msgInfo); if (err SDKERR_SUCCESS) { std::cout Private message sent std::endl; } } }5.3 富文本消息加粗、斜体等样式IChatMsgInfoBuilder提供了按字符区间施加样式的能力。区间采用从 0 开始的字符位置而非字节位置且结束位置为开区间例如对Hello, this is BOLD and this is italic加粗 BOLD字符索引 14~18调用SetBold(14, 18)斜体 italic字符索引 32~38调用SetItalic(32, 38)。void sendFormattedMessage() { if (!g_chatController) return; IChatMsgInfoBuilder* builder g_chatController-GetChatMessageBuilder(); if (!builder) return; // Set content: Hello, this is BOLD and this is italic const wchar_t* content LHello, this is BOLD and this is italic; builder-SetContent(content); builder-SetReceiver(0); builder-SetMessageType(SDKChatMessageType_To_All); // Apply bold to BOLD (positions 14-17, 0-indexed) builder-SetBold(14, 18); // Apply italic to italic (positions 32-37) builder-SetItalic(32, 38); // Build and send IChatMsgInfo* msgInfo builder-Build(); if (msgInfo) { g_chatController-SendChatMsgTo(msgInfo); } }5.4 带链接的消息通过InsertLinkAttrs结构体指定链接 URL再以SetInsertLink将链接作用到文本的指定区间同样为 0 起始的字符位置void sendMessageWithLink() { if (!g_chatController) return; IChatMsgInfoBuilder* builder g_chatController-GetChatMessageBuilder(); if (!builder) return; // Set content with link text const wchar_t* content LCheck out this website for more info; builder-SetContent(content); builder-SetReceiver(0); builder-SetMessageType(SDKChatMessageType_To_All); // Create link attributes InsertLinkAttrs linkAttrs; linkAttrs.insertLinkUrl Lhttps://zoom.us; // Apply link to this website (positions 10-21) builder-SetInsertLink(linkAttrs, 10, 22); IChatMsgInfo* msgInfo builder-Build(); if (msgInfo) { g_chatController-SendChatMsgTo(msgInfo); } }5.5 线程化回复Threaded Reply在收到消息后从IChatMsgInfo::GetThreadID()取出所属线程 ID再通过SetThreadId指定即可将新消息回复到该线程void sendThreadedReply(const wchar_t* threadId, const wchar_t* message) { if (!g_chatController) return; IChatMsgInfoBuilder* builder g_chatController-GetChatMessageBuilder(); if (!builder) return; builder-SetContent(message); builder-SetReceiver(0); builder-SetMessageType(SDKChatMessageType_To_All); builder-SetThreadId(threadId); // Reply to existing thread IChatMsgInfo* msgInfo builder-Build(); if (msgInfo) { g_chatController-SendChatMsgTo(msgInfo); } }5.6 Builder 复用与清理IChatMsgInfoBuilder可以重复使用但两次消息之间必须调用Clear()否则上一次设置的样式、接收者等属性会残留到下一封消息中。这对应原文档常见陷阱中的第 4 条是富文本消息最容易踩的坑。六、完整集成示例进入会议后自动打招呼将上述步骤串起来在IMeetingServiceEvent::onMeetingStatusChanged中检测到MEETING_STATUS_INMEETING时初始化聊天并发送一条欢迎消息。完整的IMeetingServiceEvent九个纯虚方法的实现模板见 interface-methods.mdvoid onInMeeting(IMeetingService* meetingService) { // Initialize chat when in meeting initializeChat(meetingService); // Send a greeting sendMessageToAll(LHello everyone! Bot has joined the meeting.); } // Call from your meeting status callback void MeetingServiceEventListener::onMeetingStatusChanged( MeetingStatus status, int iResult ) { if (status MEETING_STATUS_INMEETING) { onInMeeting(g_meetingService); } }关键前提Windows SDK 的所有异步回调包括onMeetingStatusChanged与onChatMsgNotification都依赖 Windows 消息泵来派发。如果主线程没有持续执行PeekMessage/GetMessage处理消息循环聊天回调永远不会触发——这并非网络问题而是消息循环缺失。主循环写法与回调不触发的排查方法详见 windows-message-loop.mdwhile (!g_exit) { MSG msg; while (PeekMessage(msg, NULL, 0, 0, PM_REMOVE)) { if (msg.message WM_QUIT) { g_exit true; break; } TranslateMessage(msg); DispatchMessage(msg); } std::this_thread::sleep_for(std::chrono::milliseconds(100)); }七、IChatMsgInfoBuilder 方法参考表下表汇总了消息构造器的全部常用方法覆盖文本内容、接收者、消息类型、线程回复、各类行内样式与段落样式MethodDescriptionSetContent(const zchar_t*)Set message text contentSetReceiver(unsigned int)Set recipient (0 everyone)SetMessageType(SDKChatMessageType)Set message type (all, individual, waiting room)SetThreadId(const zchar_t*)Set thread ID for repliesSetBold(start, end)Apply bold styleSetItalic(start, end)Apply italic styleSetUnderline(start, end)Apply underline styleSetStrikethrough(start, end)Apply strikethrough styleSetFontColor(FontColorAttrs, start, end)Set font colorSetBackgroundColor(BackgroundColorAttrs, start, end)Set background colorSetFontSize(FontSizeAttrs, start, end)Set font sizeSetInsertLink(InsertLinkAttrs, start, end)Insert hyperlinkSetBulletedList(start, end)Apply bulleted list styleSetNumberedList(start, end)Apply numbered list styleSetQuotePosition(start, end)Apply quote styleSetParagraph(ParagraphAttrs, start, end)Set paragraph style (H1, H2, H3)ClearStyles()Clear all stylesClear()Clear all propertiesBuild()Build the IChatMsgInfo object八、消息类型枚举SDKChatMessageType枚举定义了消息可发送的目标范围构建消息时通过SetMessageType指定enum SDKChatMessageType { SDKChatMessageType_To_None, // Invalid SDKChatMessageType_To_All, // To everyone SDKChatMessageType_To_Individual, // Private message SDKChatMessageType_To_Individual_Panelist, // Webinar panelist SDKChatMessageType_To_WaitingRoomUsers // To waiting room };其中SDKChatMessageType_To_Individual_Panelist用于网络研讨会Webinar场景向嘉宾单独发消息SDKChatMessageType_To_WaitingRoomUsers用于向等候室用户发消息。Webinar 相关能力的扩展说明可参考 webinars.md。九、错误处理SendChatMsgTo 返回码解析SendChatMsgTo返回SDKError应针对常见错误码分别处理SDKError err g_chatController-SendChatMsgTo(msgInfo); switch (err) { case SDKERR_SUCCESS: std::cout Message sent std::endl; break; case SDKERR_INVALID_PARAMETER: std::cerr Invalid message parameters std::endl; break; case SDKERR_NO_PERMISSION: std::cerr No permission to send chat std::endl; break; case SDKERR_WRONG_USAGE: std::cerr Chat not available (not in meeting?) std::endl; break; default: std::cerr Failed to send: err std::endl; }结合 windows-reference.md 中的错误码总表SDKERR_WRONG_USAGE通常意味着在错误的时机调用了 API如尚未进入会议就发送消息SDKERR_NO_PERMISSION说明当前账号或 App 类型没有发送聊天的权限如参会者被主持人禁言聊天。更完整的错误码表与诊断流程可查看 common-issues.md。十、常见陷阱与最佳实践Chat controller unavailable聊天控制器必须在会议中MEETING_STATUS_INMEETING才能获取和使用进入会议前请等待状态回调Position indexing样式位置是 0 起始的字符位置而非字节位置多字节字符如中文、emoji需要按字符计数否则样式会错位Unicode supportSDK 文本接口统一使用wchar_t*应用侧应使用std::wstring以保证中文等多语言内容正确传输与显示Builder reuse构造器可复用但两次消息之间必须调用Clear()清除上一次的残留属性Thread ID回复线程时从IChatMsgInfo::GetThreadID()获取线程 ID而不是自行拼接消息循环不要在主线程中仅用sleep等待回调必须持续PeekMessage/GetMessage处理 Windows 消息否则所有聊天事件都不会触发监听器完整性实现IMeetingChatCtrlEvent时必须覆盖全部纯虚方法含文件传输回调否则编译报抽象类错误可先用空实现桩占位。十一、延伸阅读chat.md — 本文对应的原始示例文档sdk-architecture-pattern.md — 适用于所有功能的三步实现公式SKILL.md — Windows SDK 总导航与工程配置vcpkg、Visual Studio 属性、config.jsonwindows-message-loop.md — 回调不触发的根因分析与修复interface-methods.md — 全部纯虚方法清单与实现模板windows-reference.md — 依赖安装、错误码表与 SDK 接口参考authentication-pattern.md — 认证与进入会议的完整工作流说明本文内容基于仓库文档所对应的 Zoom Windows Meeting SDK v6.7.2.26830 编写不同 SDK 版本的回调方法数量与接口签名可能存在差异升级版本后请以实际头文件为准。【免费下载链接】knowledge-work-pluginsOpen source repository of plugins primarily intended for knowledge workers to use in Claude Cowork项目地址: https://gitcode.com/GitHub_Trending/kn/knowledge-work-plugins创作声明：本文部分内容由AI辅助生成（AIGC），仅供参考