Skip to main content

Raymond Chen from Microsoft has a great answer on his blog:

https://devblogs.microsoft.com/oldnewthing/?p=36423on his blog:

“One danger of the MsgWaitForMultipleObjects function is calling it when there are already messages waiting to be processed, because MsgWaitForMultipleObjects returns only when there is a new event in the queue.”

One danger of the MsgWaitForMultipleObjects function is calling it when there are already messages waiting to be processed, because MsgWaitForMultipleObjects returns only when there is a new event in the queue.

His blog is a great read!

Raymond Chen from Microsoft has a great answer on his blog:

https://devblogs.microsoft.com/oldnewthing/?p=36423

“One danger of the MsgWaitForMultipleObjects function is calling it when there are already messages waiting to be processed, because MsgWaitForMultipleObjects returns only when there is a new event in the queue.”

His blog is a great read!

Raymond Chen from Microsoft has a great answer on his blog:

One danger of the MsgWaitForMultipleObjects function is calling it when there are already messages waiting to be processed, because MsgWaitForMultipleObjects returns only when there is a new event in the queue.

His blog is a great read!

Source Link
rwbaskette
  • 355
  • 1
  • 3

Raymond Chen from Microsoft has a great answer on his blog:

https://devblogs.microsoft.com/oldnewthing/?p=36423

“One danger of the MsgWaitForMultipleObjects function is calling it when there are already messages waiting to be processed, because MsgWaitForMultipleObjects returns only when there is a new event in the queue.”

His blog is a great read!