From f743e54453be1fbf9b7510b46ace93170ab5eabf Mon Sep 17 00:00:00 2001 From: Graeme Geldenhuys Date: Mon, 11 Oct 2010 11:27:51 +0200 Subject: fpgApplication.ProcessMessages now process other events (eg: timers) too. The DoMessagesPending() only processed OS events, now ProccessMessages processes all events like the real event loop does. This gives a more expected behaviour to developers that write blocking loops etc. --- src/corelib/fpg_main.pas | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'src/corelib') diff --git a/src/corelib/fpg_main.pas b/src/corelib/fpg_main.pas index c89dc51d..08885567 100644 --- a/src/corelib/fpg_main.pas +++ b/src/corelib/fpg_main.pas @@ -1516,11 +1516,11 @@ end; procedure TfpgApplication.ProcessMessages; begin Flush; - while DoMessagesPending do - begin - WaitWindowMessage(0); - Flush; - end; +// while DoMessagesPending do // this blocked timers and other non-OS code +// begin + WaitWindowMessage(250); +// Flush; +// end; end; procedure TfpgApplication.SetMessageHook(AWidget: TObject; const AMsgCode: integer; AListener: TObject); -- cgit v1.2.3-70-g09d2