[Lazarus] sleep function don't passed before executing the next statement

[Mark Morgan Lloyd]

Michael Schnell wrote:
> On 11/21/2012 09:35 AM, Bernd wrote:
>> You should generally try your best to avoid using Sleep() in the above 
>> way in most cases.
> I would go so fat saying that in a GUI project sleep in the main thread 
> is strictly forbidden, as it produces nothing but confusion.
> 
> (Same is true for any "busy wait" polling loops in the main thread and 
> "busy wait" polling loops without sleep in worker threads.)

Also much database stuff in my experience. *Anything* which doesn't 
return immediately is very bad news from a usability POV.

-- 
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk

[Opinions above are the author's, not those of his employers or colleagues]