Arno Garrels wrote: > Arno Garrels wrote: > >>> I don't think it could be a problem. But f it does, GetQueueStatus >>> can be called to know if there is a WM_TIMER message already in the >>> queue. > > Did some testing with sending 1000 SendNotifyMessages to the main > thread per second. Then I paused message processing for 10 seconds > by holding the [X] system button pressed. CPU use increased to ~50% > and entire system became very slow, almost non-responsive, I had to > kill the process which took me several minutes while CPU temperature > was in the red area. > > Same test with PostMessage works without this effect however > the queue size is limited (10.000 messages) by default, so any > subsequent call to PostMessage fails, which was a disaster as well.
I found an easy workaround, please forget this message. -- Arno Garrels -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
