Win32 CreateWindow() 调用在子线程中挂起?
我正在为 OpenGL 开发一个可移植层(为 Linux 和 Windows 抽象出 glX 和 wgl 的东西)...无论如何,它有一个创建窗口的方法...如果你不传入父级,你会得到一个带有框架的真实窗口...如果你传入一个父窗口,你会得到一个无边框、无框架的窗口...
这工作正常,只要我在 1 个线程上完成这一切...一旦另一个线程尝试创建子窗口时,应用程序在 win32 调用“CreateWindow()”时死锁。有什么想法吗?
I'm working on a portability layer for OpenGL (abstracts the glX and wgl stuff for Linux and Windows)... Anyhow, it has a method for creating a Window... If you don't pass in a parent, you get a real window with a frame... If you pass in a parent, you get a borderless, frameless window...
This works fine, as long as I do it all on 1 thread... As soon as another thread tries to create a child window, the app deadlocks in the win32 call "CreateWindow()". Any ideas?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(5)
这不是一个真正的答案,但由于很多人似乎认为 Win32 禁止在父线程之外的其他线程中创建子线程,所以我觉得有必要发布一个相反的演示。
下面的代码演示了在属于不同进程的父级上创建子窗口。它接受窗口句柄值作为命令行参数,并在该父窗口上创建子窗口。
使用以下命令进行编译(使用 MSVC 命令行环境):
然后使用 Spy++ 或其他一些工具来获取任何窗口的句柄值——例如记事本或您正在查看此站点的浏览器的句柄值。假设它是 0x00001234。然后使用 t.exe 0x1234 运行已编译的示例。使用 Ctrl-C 终止 t.exe(或仅关闭控制台窗口)。
This is not a real answer, but since so many people seem to believe that Win32 forbids creating children in other threads than the parent, I feel obliged to post a demonstration to the contrary.
The code below demonstrates creation of a child window on a parent belonging to a different process. It accepts a window handle value as a command-line parameter and creates a child window on that parent.
Compile this with the following command (using MSVC command line environment):
Then use Spy++ or some other tool to obtain handle value of any window -- e.g. of Notepad or the browser you're viewing this site in. Let's assume it's 0x00001234. Then run the compiled sample with
t.exe 0x1234
. Use Ctrl-C to terminate t.exe (or just close the console window).当子窗口创建后,它可以通过
SendMessage
与父窗口交互。但是,请注意,与PostMessage
不同,跨线程边界的SendMessage
会阻塞线程。如果父窗口的线程正在等待子线程,而子线程试图创建一个父窗口在该线程中的窗口,那么就会出现死锁。一般来说,我认为跨线程建立子父关系不是一个好主意。它很容易造成僵局。
When a child window is created, it can interact with the parent window via
SendMessage
. But, note thatSendMessage
across thread boundary blocks threads unlikePostMessage
. If the parent window's thread is waiting for the child thread, and the child thread is trying to create a window whose parent is in that thread, then it's a deadlock.In general, I don't think it's a good idea to make child-parent relationship across the threads. It can very easily make deadlock.
这里有很多回复说你不能尝试在不同的线程上拥有子窗口和父窗口,并且强调它不会工作。
如果是这样,Windows 将采取一些保护措施,并且当您尝试调用 CreateWindow 时就会失败。
现在,肯定存在可能导致重大问题的线程耦合问题,但是,考虑到这些限制,这是受支持的场景。
There are a lot of replies here saying that you MUST NOT attempt to have child and parent windows on different threads, and rather emphatically stating that it will not work.
If that was so, Windows would put some safeguards in and simply fail out when you attempted to call CreateWindow.
Now, there definitely are thread coupling issues that can cause major issues, but, that said with those constraints, this is a supported scenario.
这是一个有趣的问题:很多老派的 win32 人告诉我你不能这样做。在研究这个问题时,我发现了这个论坛: SendMessage()。我目前的理论是 CreateWindowEx() 必须向父窗口发送一条消息(通过 SendMessage(),因此它会阻塞),以请求存在的权限(或至少通知其存在)...无论如何,只要该父线程可以自由地处理这些消息,一切正常......
This is an interesting question: A lot of old school win32 guys have told me you CANNOT do this. In researching this, I found this forum: SendMessage(). My current theory is that CreateWindowEx() must send a message (via SendMessage(), so it blocks) to the parent window to ask for permission to exist (or at least to notify of its existence)... Anyhow, as long as that parent thread is free to process these messages, it all works...
窗口与创建它的线程相关联(更具体地说,与该线程的消息队列相关联)。父窗口不能与其子窗口驻留在不同的线程中。
A window is tied to the thread that creates it (more specifically, to that thread's message queue). A parent window cannot reside in a different thread than its child windows.