The Dark Side of Application.ProcessMessages in Delphi Applications

<p>in <a Stuff</i></a> :: <a /></a></p> <p>When coding an event handler in Delphi (like the OnClick event of a TButton), there comes the time when your application needs to be busy for a while, e.g. the code needs to write a big file or compress some data. If you do that notice that your application seems to be locked. <p>Your form cannot be moved anymore and the buttons are showing no sign of life. It seems to be crashed. Application.ProcessMessages might come as a rescue, but you need to know its dark side!</p> <p>Read the <b>full article</b> to learn <b><a and when not to use Application.ProcessMessages</a></b></p> <p><b>Related:</b></p> <ul Container Child Controls when the Enabled Property Changes</a></li> <li><a in Delphi</a></li> <li><a Windows Messages the Delphi way</a></li> </ul>

Read More...

---