02-25-2013, 03:25 PM
I don't have much experience in this. I think everything here is correct.
It's easy to switch to other thread with SendMessage or PostMessage. COM object's thread creates a hidden message-only window, and HTTP server's thread sends messages to it.
Don't forget that QM macro must process messages. If it is a dialog or other window, or has a message loop, it already processes messages. Else need opt waitmsg 1 and wait().
Or HTTP server's thread could call a QM function as a callback function in its thread. Then don't need events. And QM macro does not have to process messages.
It's easy to switch to other thread with SendMessage or PostMessage. COM object's thread creates a hidden message-only window, and HTTP server's thread sends messages to it.
Don't forget that QM macro must process messages. If it is a dialog or other window, or has a message loop, it already processes messages. Else need opt waitmsg 1 and wait().
Or HTTP server's thread could call a QM function as a callback function in its thread. Then don't need events. And QM macro does not have to process messages.