-=> Quoting Ron Tuynman to Robert Lamping <=-
 Dear Ron,
 You replied:
 RL> A clock in the upper right corner is simply defined with:
 RL> define bgevent action clock() 
 RL> And the function:
 
 RL> Function clock()
 RL> Local nRow := row()
 RL> Local nCol := col()
 RL> @ 0,72 say time()
 RL> Devpos( nRow, nCol)
 RL> Return NIL
 
 RT> ...It's all right as long as your program does JUST THAT in an
 RT> endless loop.
 It doesn't do that.
 RT> But as soon as you put a waitstate somewhere (GET...READ, MENU TO,
 RT> ACHOICE, INKEY) the clock stops and only gets active again AFTER the
 RT> input...
 Don't be missled by the command, there are function which replace the 
 command!
 I have the strong impression you didn't compile and link the file test2.prg.
 The batchfile m.bat helps you to easy up the compiling and linking.
 It is also possible that you don't have the latest version.
 BGEVENTS works properly with version Clipper 5.2 and 5.3. 
 
 Did you really try to link the test2.prg program and see what happens?
 There is a first GET and 5 clocks. After five seconds, by Pressing F12, 
 another program starts with another GET and the clocks still continue to 
work. 
 The eventhandler in version BGEV2a.zip has been made reentrant by Arno 
 Arno Tolmeijer.
 RT> No, a clock can only be done by hanging it on an interrupt, which
 RT> can't be done in pure Clipper. 
 We used C v.8.0  !
 RT> But there are plenty LIB's with
 RT> functions that do so for you....
 And so does events.c. It is able to insert a Clipper function into the 
 Clipper main-loop of the application. All DOS applications have such a loop.
 RT> Nice try...
 Please try it again, I am looking forward to your response. 
 The latest version with a lot of documentation you can find at:
    http://www.stack.nl/~lamping/bgevents.htm
 Good luck and thank you very much for your message!
 Kind regards,
 Robert Lamping
 The Netherlands
 
--- Blue Wave v2.12 [NR]
---------------