.NET Winforms Waitmessage() is misleading in purepaths
I have a .NET rich client application (both winforms and WPF), which shows a lot of winforms waitmessage() calls in the purepaths, some of these last 20 seconds or longer. I would think that waitmessage() should end the purepath, since the thread is suspended. Is anyone else seeing this behavior?
After further investigation, I think this may be more an issue with modal dialogs, these waitmessage() calls are inside rundialog() calls.
Hi Mark
You are right. These methods unfortunately show up as main hotspots even though all they really do is wait for e.g: another thread to complete or - as it is in your case - the user input
Andi
