PC Toledo

They do the same, but I'm not sure, that hwg_DoEvents() processes
messages for dialogs and mdi windows ( Hwg_ProcessMessage() has a
special code for them ).
Additionally, Hwg_ProcessMessage() contains a sleep() function call.
The second parameter of Hwg_ProcessMessage() designates a number of
milliseconds to sleep, it is 1 by default. It was introduced for the
program do not eat too much processor time in a big cycles. You may try
to set this parameter to 0. Other option, which I use, is to call the
Hwg_ProcessMessage() not in each cycle iteration, but in 1 of 10, or
even 1 of 100. There is no any need to check messages after every skip.

Regards, Alexander.

ProcessMessage() e Hwg_DoEvents()

DO WHILE !EOF()

SKIP
ProcessMessage()

ENDDO

nCiclo := 0
DO WHILE !EOF()

SKIP

If ++nCiclo == 100
   ProcessMessage()
   nCiclo := 0
endif

ENDDO