Why is this happening? The technique of processing all events in a
second thread works fine under Linux.
I’m now thinking about swapping the threads, just processing the events
in the original one and running the game in a second one…
As explained in the other message, there’s no way of accessing the
event queue for the window from another thread, or transferring ownership
of the window to another thread (if this isn’t the case, PLEASE let know!
As I mentioned, there is a way, to do this. The function is called
AttachThreadInput and pipes the complete message loop to another thread:
DWORD idAttach, // ID of thread to be chown
DWORD idAttachTo, // ID of thread to recieve the input
BOOL fAttach // establish or destroy the pipe?
Don’t know, if that solves the mentioned problem internally, but this should
be at least an attempt.
Andreas PodgurskiOn Tue, 17 Oct 2000 16:46:05 -0700, Sam Lantinga wrote: