Comments on: Telling Windows we’re not really “Not Responding” http://blog.excastle.com/2005/08/15/telling-windows-were-not-really-not-responding/ Life, .NET, and Cats Mon, 08 Sep 2008 15:05:40 +0000 http://wordpress.org/?v=2.5 By: Pradeep http://blog.excastle.com/2005/08/15/telling-windows-were-not-really-not-responding/#comment-5401 Pradeep Tue, 19 Dec 2006 15:55:00 +0000 http://blog.excastle.com/2005/08/15/telling-windows-were-not-really-not-responding/#comment-5401 hello , I also face above problem. any body have any soluton for winxp ? hello , I also face above problem. any body have any soluton for winxp ?

]]> By: Joe White http://blog.excastle.com/2005/08/15/telling-windows-were-not-really-not-responding/#comment-5400 Joe White Wed, 17 Aug 2005 10:26:00 +0000 http://blog.excastle.com/2005/08/15/telling-windows-were-not-really-not-responding/#comment-5400 Already thought of that, but the <a target="_new" href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/winui/winui/windowsuserinterface/windowing/messagesandmessagequeues/messagesandmessagequeuesreference/messagesandmessagequeuesfunctions/peekmessage.asp" rel="nofollow">MSDN docs for PeekMessage</a> say that it's only for windows that belong to the current thread: if you specify a window handle, it has to belong to the current thread; and if you pass NULL for a window handle (as this code does), it will only read messages for windows belonging to the current thread. So I don't think calling PeekMessage from a secondary thread would do any good for windows that belong to the primary thread (though I didn't actually try it). Already thought of that, but the MSDN docs for PeekMessage say that it’s only for windows that belong to the current thread: if you specify a window handle, it has to belong to the current thread; and if you pass NULL for a window handle (as this code does), it will only read messages for windows belonging to the current thread. So I don’t think calling PeekMessage from a secondary thread would do any good for windows that belong to the primary thread (though I didn’t actually try it).

]]> By: Jim McKeeth http://blog.excastle.com/2005/08/15/telling-windows-were-not-really-not-responding/#comment-5399 Jim McKeeth Tue, 16 Aug 2005 14:50:00 +0000 http://blog.excastle.com/2005/08/15/telling-windows-were-not-really-not-responding/#comment-5399 Why not just put a call in your TellWindowsWeArentFrozen in a seperate thread and have that thread call every second (less frequent then every 15 ms, but more then every 5 seconds). Since that other thread doesn't do anything with the message is peeks it wouldn't cause any multi-threaded issues. <br> <br>This is also not a "right" solution, but it would fix your symptom without requiring you to modify all your long running data processing code. Why not just put a call in your TellWindowsWeArentFrozen in a seperate thread and have that thread call every second (less frequent then every 15 ms, but more then every 5 seconds). Since that other thread doesn’t do anything with the message is peeks it wouldn’t cause any multi-threaded issues.

This is also not a "right" solution, but it would fix your symptom without requiring you to modify all your long running data processing code.

]]>