X11
Tk(Tkinter 下的库)的 X11 实现的底部是这段代码 https://github.com/tcltk/tk/blob/50c34e54dc3e5a32c2c712809d133b23b99f5e12/unix/tkUnixWm.c#L6326,我将其复制在这里,没有注释:
void
TkWmProtocolEventProc(
TkWindow *winPtr,
XEvent *eventPtr)
{
WmInfo *wmPtr;
ProtocolHandler *protPtr;
Atom protocol;
int result;
const char *protocolName;
Tcl_Interp *interp;
protocol = (Atom) eventPtr->xclient.data.l[0];
if (protocol == Tk_InternAtom((Tk_Window) winPtr, "_NET_WM_PING")) {
Window root = XRootWindow(winPtr->display, winPtr->screenNum);
eventPtr->xclient.window = root;
(void) XSendEvent(winPtr->display, root, False,
(SubstructureNotifyMask|SubstructureRedirectMask), eventPtr);
return;
}
wmPtr = winPtr->wmInfoPtr;
if (wmPtr == NULL) {
return;
}
protocolName = Tk_GetAtomName((Tk_Window) winPtr, protocol);
for (protPtr = wmPtr->protPtr; protPtr != NULL;
protPtr = protPtr->nextPtr) {
if (protocol == protPtr->protocol) {
Tcl_Preserve(protPtr);
interp = protPtr->interp;
Tcl_Preserve(interp);
result = Tcl_EvalEx(interp, protPtr->command, -1, TCL_EVAL_GLOBAL);
if (result != TCL_OK) {
Tcl_AppendObjToErrorInfo(interp, Tcl_ObjPrintf(
"\n (command for \"%s\" window manager protocol)",
protocolName));
Tcl_BackgroundException(interp, result);
}
Tcl_Release(interp);
Tcl_Release(protPtr);
return;
}
}
if (protocol == Tk_InternAtom((Tk_Window) winPtr, "WM_DELETE_WINDOW")) {
Tk_DestroyWindow((Tk_Window) wmPtr->winPtr);
}
}
基本上,Tk 只真正处理_NET_WM_PING
(它会为你做出响应 - 如果你在这个处理程序中,事件循环正在运行,这就是该协议正在检查的内容)和WM_DELETE_WINDOW
,但它也可以处理任何工作原理完全相同的协议WM_DELETE_WINDOW
在消息级别。特别是,您无权访问事件的字段(隐式访问除外),并且无法发送对任何内容的响应。这意味着它可以处理WM_SAVE_YOURSELF
(旧的会话管理协议)但不能这样做WM_TAKE_FOCUS
(并且不需要;Tk 有自己的焦点管理,就像当今的所有其他应用程序一样)。我们欢迎实施_NET_WM_SYNC_REQUEST https://specifications.freedesktop.org/wm-spec/wm-spec-1.3.html#idm45643490036528,但这不是一个高优先级。
Windows
在 Windows 上,有一些额外的处理。尤其,WM_HELP
看起来应该由以下人员处理TkTranslateWinEvent https://github.com/tcltk/tk/blob/50c34e54dc3e5a32c2c712809d133b23b99f5e12/win/tkWinX.c#L842.
int
TkTranslateWinEvent(
HWND hwnd,
UINT message,
WPARAM wParam,
LPARAM lParam,
LRESULT *resultPtr)
{
*resultPtr = 0;
switch (message) {
case WM_RENDERFORMAT: {
TkWindow *winPtr = (TkWindow *) Tk_HWNDToWindow(hwnd);
if (winPtr) {
TkWinClipboardRender(winPtr->dispPtr, wParam);
}
return 1;
}
case WM_RENDERALLFORMATS: {
TkWindow *winPtr = (TkWindow *) Tk_HWNDToWindow(hwnd);
if (winPtr && OpenClipboard(hwnd)) {
if (GetClipboardOwner() == hwnd) {
TkWinClipboardRender(winPtr->dispPtr, CF_TEXT);
}
CloseClipboard();
}
return 1;
}
case WM_COMMAND:
case WM_NOTIFY:
case WM_VSCROLL:
case WM_HSCROLL: {
HWND target = (message == WM_NOTIFY)
? ((NMHDR*)lParam)->hwndFrom : (HWND) lParam;
if (target && target != hwnd) {
*resultPtr = SendMessageW(target, message, wParam, lParam);
return 1;
}
break;
}
case WM_LBUTTONDOWN:
case WM_LBUTTONDBLCLK:
case WM_MBUTTONDOWN:
case WM_MBUTTONDBLCLK:
case WM_RBUTTONDOWN:
case WM_RBUTTONDBLCLK:
case WM_XBUTTONDOWN:
case WM_XBUTTONDBLCLK:
case WM_LBUTTONUP:
case WM_MBUTTONUP:
case WM_RBUTTONUP:
case WM_XBUTTONUP:
case WM_MOUSEMOVE:
TkWinPointerEvent(hwnd, (short) LOWORD(lParam), (short) HIWORD(lParam));
return 1;
case WM_SYSKEYDOWN:
case WM_KEYDOWN:
if (wParam == VK_PACKET) {
*resultPtr =
PostMessageW(hwnd, message, HIWORD(lParam), LOWORD(lParam));
return 1;
}
/* fall through */
case WM_CLOSE:
case WM_SETFOCUS:
case WM_KILLFOCUS:
case WM_DESTROYCLIPBOARD:
case WM_UNICHAR:
case WM_CHAR:
case WM_SYSKEYUP:
case WM_KEYUP:
case WM_MOUSEWHEEL:
case WM_MOUSEHWHEEL:
GenerateXEvent(hwnd, message, wParam, lParam);
return 1;
case WM_MENUCHAR:
GenerateXEvent(hwnd, message, wParam, lParam);
*resultPtr = MAKELONG (0, MNC_CLOSE);
return 1;
}
return 0;
}
如您所见,它无法处理它。如果是的话,将其映射以生成<KeyPress-Help>
event 可能是正确的方法(是的,这是一个真实的事件,由于标准键盘布局不同,您在 Windows 上永远不会看到该事件)。这还需要更改GenerateXEvent
(同一文件,就在下面)。
我不知道是什么DefWindowProcW
与WM_HELP
;这是 Windows 中事件的最后手段,而且这肯定是这些事件目前正在发生的地方。
改变其中任何一个is可能,但确实需要一点 GUI 编程水平的 C 编程,而几乎没有人从事这种工作。补丁可以提交至https://core.tcl-lang.org/tk/tktnew https://core.tcl-lang.org/tk/tktnew(我建议针对core-8-5-branch
在这种情况下,因为我认为这是一个小的功能更改,可以放入旧版本的补丁中)。