检测窗口关闭wndproc外面？-Detectwindowcloseoutsideofwndproc?

How about this: periodically spin a message loop to dispatch any messages on the message queue (that'll cause mouse/input messages to be handled which will generate the WM_CLOSE). In your app's main window set a flag when WM_CLOSE is received and check that flag after spinning the loop.

怎么样:定期旋转一个消息循环来调度消息队列上的任何消息(这将导致处理鼠标/输入消息,这将生成WM_CLOSE)。在应用程序的主窗口中,收到WM_CLOSE时设置一个标志,并在旋转循环后检查该标志。

Simplest case of spinning a message loop to flush any pending messages would be:

旋转消息循环以刷新任何待处理消息的最简单情况是:

while (PeekMessage(&msg, NULL, 0, 0, PM_REMOVE))
{
    TranslateMessage(&msg);
    DispatchMessage(&msg);
}

though your app frame work may already have functions to do this. Hope this helps.

虽然您的应用程序框架工作可能已经具有执行此操作的功能希望这可以帮助。

Would you consider adding another thread redesigning the application? It certainly would make your life much easier! Just let the Gui do all the Gui stuff and run it's message loop and do all the hard work in another thread. If the user wants to quit the application, present him a nice OK/Cancel message and suspend/abort the "worker thread" accordingly. Handling two separate tasks in this one thread - with all the workarounds - will make things way more messier than it has to be. Good luck!

您会考虑添加另一个重新设计应用程序的线程吗?它肯定会让你的生活更轻松!只需让Gui做所有的Gui东西并运行它的消息循环并在另一个线程中完成所有艰苦的工作。如果用户想要退出应用程序,请向他显示一个很好的确定/取消消息并相应地暂停/中止“工作线程”。在这一个线程中处理两个单独的任务 - 使用所有的解决方法 - 将使事情变得更加混乱。祝好运!

I guess you can keep handling your WM_ CLOSE message in the wndproc, and when you receive it you call PostQuitMessage(), which in turn will generate a WM_ QUIT message that in turn will be read by GetMessage()/PeekMessage().

我猜你可以继续在wndproc中处理你的WM_ CLOSE消息,当你收到它时你调用PostQuitMessage(),然后它会生成一个WM_QUIT消息,而这个消息又将被GetMessage()/ PeekMessage()读取。

If your window thread is completely blocked, you're out of luck. You have a few options. The thread must be able to periodically do PeekMessage() while in "script engine mode".

如果你的窗口线程被完全阻止,那你就不走运了。你有几个选择。在“脚本引擎模式”下,线程必须能够定期执行PeekMessage()。

while (IsScripting()) {
    ScriptEngineTimeSlice();
    while (PeekMessage( .. )) {
        TranslateMessage( .. );
        DispatchMessage( .. ); // <-- wnd procedure will be called
        // ..
    }
}

This is probabably old news for you, since you already are aware of this. But if you somehow can't give the UI thread a break, there is no way to solve this. If the thread is blocked, it's blocked.

这对你来说可能是个新闻,因为你已经意识到了这一点。但是如果你以某种方式无法让UI线程中断,那么就无法解决这个问题。如果线程被阻止,则被阻止。

If you are debugging, wouldn't that mean the user was debugging? Why would they be surprised that the app was then "not responding"? Anyway, you have control of the window procedure for the window, so why not just watch for the WM_CLOSE message in there? It is your window?

如果您正在调试,那是不是意味着用户正在调试?为什么他们会对应用程序“没有响应”感到惊讶?无论如何,您可以控制窗口的窗口过程,那么为什么不在那里查看WM_CLOSE消息呢?这是你的窗户?