Am 18.01.2016 um 18:35 schrieb Robert M. Münch:

On 2016-01-18 12:10:07 +0000, Snke Ludwig said:

Hum, the message window only really needs to process the messages that
are directly sent to it, namely the WM_USER_SIGNAL and
WM_USER_SOCKET messages. Did those somehow not reach the window once
you added your own? I never had issues so far.

Maybe I'm doing things wrong even it works. So, AFAIU one app can't have
several windows that are not related either by subclassing, parenting etc.

Or can I just register my own window class, open a new window and the
vibe message loop will work?

I've never had an issue with the latter approach. My understanding is
that the message queue can hold messages for any number of otherwise
unrelated windows created by the calling thread. GetMessage with a
NULL hWnd parameter receives any of those, and DispatchMessage
dispatches to the window procedure associated with their respective
window class.